--- gvpe/doc/gvpe.osdep.5.pod	2005/03/23 21:55:39	1.8
+++ gvpe/doc/gvpe.osdep.5.pod	2005/06/21 08:46:53	1.11
@@ -7,7 +7,7 @@
 This file tries to capture OS-dependent configuration or build issues,
 quirks and platform limitations, as known.
 
-=head2 TUN vs. TAP interface
+=head1 TUN vs. TAP interface
 
 Most operating systems nowadays support something called a
 I<tunnel>-device, which makes it possible to divert IPv4 (and often other
@@ -30,13 +30,15 @@
 possible), or you need to send a packet from these hosts into the vpn
 network to tell gvpe the local interface address.
 
-=head2 Interface Initialisation
+=head1 Interface Initialisation
 
-Unless otherwise notes, the network interface will be set "UP" with the
-correct MAC address and correct MTU value. With most interface drivers,
+Unless otherwise notes, the network interface will be initialized with the
+expected MAC address and correct MTU value. With most interface drivers,
 this is done by running C</sbin/ifconfig>, so make sure that this command
 exists.
 
+=head1 Interface Types
+
 =head2 native/linux
 
 TAP-device; already part of the kernel (only 2.4+ supported, but see
@@ -74,6 +76,15 @@
 The MAC address is dynamically being patched into packets and
 ARP-requests, so only IPv4 works with ARP on this platform.
 
+=head2 tincd/bsd
+
+TAP-device, maybe; migth work for many bsd variants.
+
+This driver is a newer version of the C<tincd/*bsd> drivers. It I<might>
+provide a TAP device, or might not work at all. You might try this
+interface type first, and, if it doesn't work, try one of the OS-specific
+drivers.
+
 =head2 tincd/freebsd
 
 TAP-device; part of the kernel (since 4.x, maybe earlier).
@@ -199,5 +210,5 @@
 
 =head1 AUTHOR
 
-Marc Lehmann <gvpe@plan9.de>
+Marc Lehmann <gvpe@schmorp.de>