From: Rafael Sadowski <rafael@sizeofvoid.org>
Date: Mon, 1 Oct 2018 13:14:24 +0000 (+0200)
Subject: OpenBSD has a proper tap device.
X-Git-Tag: release-1.0.35~1
X-Git-Url: https://tinc-vpn.org/git/browse?a=commitdiff_plain;h=9fac7adb587a455c14d2dccd33e5a910534a4c53;p=tinc

OpenBSD has a proper tap device.
---

diff --git a/doc/tinc.texi b/doc/tinc.texi
index f16e6723..b1f5d9d0 100644
--- a/doc/tinc.texi
+++ b/doc/tinc.texi
@@ -2075,7 +2075,7 @@ In switch or hub modes ARP does work so the sender already knows the correct des
 In those modes every interface should have a unique MAC address, so make sure they are not the same.
 Because switch and hub modes rely on MAC addresses to function correctly,
 these modes cannot be used on the following operating systems which don't have a `tap' style virtual network device:
-OpenBSD, NetBSD, Darwin and Solaris.
+NetBSD, Darwin and Solaris.
 
 
 @c ==================================================================
@@ -2500,13 +2500,6 @@ For IPv6 addresses:
 @tab @code{netsh interface ipv6 add address} @var{interface} @code{static} @var{address}/@var{prefixlength}
 @end multitable
 
-On some platforms, when running tinc in switch mode, the VPN interface must be set to tap mode with an ifconfig command:
-
-@multitable {Darwin (Mac OS X)} {ifconfig route add -bla network address netmask netmask prefixlength interface}
-@item OpenBSD
-@tab @code{ifconfig} @var{interface} @code{link0}
-@end multitable
-
 On Linux, it is possible to create a persistent tun/tap interface which will
 continue to exist even if tinc quit, although this is normally not required.
 It can be useful to set up a tun/tap interface owned by a non-root user, so