--- gvpe/doc/gvpe.osdep.5.pod 2005/03/25 15:38:07 1.9 +++ gvpe/doc/gvpe.osdep.5.pod 2008/09/01 05:31:28 1.12 @@ -11,7 +11,7 @@ Most operating systems nowadays support something called a I-device, which makes it possible to divert IPv4 (and often other -protocols, too) into a userspace daemon like C. This is being +protocols, too) into a user space daemon like C. This is being referred to as a TUN-device. This is fine for point-to-point tunnels, but for a virtual ethernet, an @@ -76,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 drivers. It I +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). @@ -160,7 +169,7 @@ See C for more information. -Completely unstested so far. +Completely untested so far. =head2 tincd/mingw @@ -181,12 +190,12 @@ =head2 tincd/uml_socket -TAP-device; purpose unknown and untested, probably creates a unix datagram +TAP-device; purpose unknown and untested, probably creates a UNIX datagram socket (path given by C) and reads and writes raw packets, so might be useful in other than UML contexts. No network interface is created, and the MAC and MTU must be set as -approriate on the other side of the socket. GVPE will exit if the MAC +appropriate on the other side of the socket. GVPE will exit if the MAC address doesn't match what it expects. Completely untested so far. @@ -201,5 +210,5 @@ =head1 AUTHOR -Marc Lehmann +Marc Lehmann