X-Git-Url: https://tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2Ftinc.texi;h=3bb4407604c46be144621b352f18990343b25cf9;hp=817c2dedcb05872ea31be34a1ad2a397c65c37b4;hb=d1dcdf8eb6f800704be426b1ce6f6c1a8e65ba0d;hpb=9f6a96af3939bd2de410ce346a8c8fbcf93e7c9b

diff --git a/doc/tinc.texi b/doc/tinc.texi
index 817c2ded..3bb44076 100644
--- a/doc/tinc.texi
+++ b/doc/tinc.texi
@@ -834,25 +834,25 @@ Also, in case tinc does not seem to correctly interpret packets received from th
 it can be used to change the way packets are interpreted:
 
 @table @asis
-@item tun (BSD only)
+@item tun (BSD and Linux)
 Set type to tun.
 Depending on the platform, this can either be with or without an address family header (see below).
 
 @cindex tunnohead
-@item tunnohead (BSD only)
+@item tunnohead (BSD)
 Set type to tun without an address family header.
 Tinc will expect packets read from the virtual network device to start with an IP header.
 On some platforms IPv6 packets cannot be read from or written to the device in this mode.
 
 @cindex tunifhead
-@item tunifhead (BSD only)
+@item tunifhead (BSD)
 Set type to tun with an address family header.
 Tinc will expect packets read from the virtual network device
 to start with a four byte header containing the address family,
 followed by an IP header.
 This mode should support both IPv4 and IPv6 packets.
 
-@item tap (BSD only)
+@item tap (BSD and Linux)
 Set type to tap.
 Tinc will expect packets read from the virtual network device
 to start with an Ethernet header.