ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/doc/gvpe.osdep.5.pod
(Generate patch)

Comparing gvpe/doc/gvpe.osdep.5.pod (file contents):
Revision 1.8 by pcg, Wed Mar 23 21:55:39 2005 UTC vs.
Revision 1.12 by pcg, Mon Sep 1 05:31:28 2008 UTC

… …
5=head1 DESCRIPTION 5=head1 DESCRIPTION
6 6
7This file tries to capture OS-dependent configuration or build issues, 7This file tries to capture OS-dependent configuration or build issues,
8quirks and platform limitations, as known. 8quirks and platform limitations, as known.
9 9
10=head2 TUN vs. TAP interface 10=head1 TUN vs. TAP interface
11 11
12Most operating systems nowadays support something called a 12Most operating systems nowadays support something called a
13I<tunnel>-device, which makes it possible to divert IPv4 (and often other 13I<tunnel>-device, which makes it possible to divert IPv4 (and often other
14protocols, too) into a userspace daemon like C<gvpe>. This is being 14protocols, too) into a user space daemon like C<gvpe>. This is being
15referred to as a TUN-device. 15referred to as a TUN-device.
16 16
17This is fine for point-to-point tunnels, but for a virtual ethernet, an 17This is fine for point-to-point tunnels, but for a virtual ethernet, an
18additional ethernet header is needed. This functionality (called a TAP 18additional ethernet header is needed. This functionality (called a TAP
19device here) is only provided by a subset of the configurations. 19device here) is only provided by a subset of the configurations.
… …
28found on a specific host, you will either need to hardwire the MAC address 28found on a specific host, you will either need to hardwire the MAC address
29for TUN-style hosts on all networks (and avoid ARP altogether, which is 29for TUN-style hosts on all networks (and avoid ARP altogether, which is
30possible), or you need to send a packet from these hosts into the vpn 30possible), or you need to send a packet from these hosts into the vpn
31network to tell gvpe the local interface address. 31network to tell gvpe the local interface address.
32 32
33=head2 Interface Initialisation 33=head1 Interface Initialisation
34 34
35Unless otherwise notes, the network interface will be set "UP" with the 35Unless otherwise notes, the network interface will be initialized with the
36correct MAC address and correct MTU value. With most interface drivers, 36expected MAC address and correct MTU value. With most interface drivers,
37this is done by running C</sbin/ifconfig>, so make sure that this command 37this is done by running C</sbin/ifconfig>, so make sure that this command
38exists. 38exists.
39
40=head1 Interface Types
39 41
40=head2 native/linux 42=head2 native/linux
41 43
42TAP-device; already part of the kernel (only 2.4+ supported, but see 44TAP-device; already part of the kernel (only 2.4+ supported, but see
43tincd/linux). This is the configuration tested best, as gvpe is being 45tincd/linux). This is the configuration tested best, as gvpe is being
… …
72 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\<adapterid>\Connection\Name 74 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\<adapterid>\Connection\Name
73 75
74The MAC address is dynamically being patched into packets and 76The MAC address is dynamically being patched into packets and
75ARP-requests, so only IPv4 works with ARP on this platform. 77ARP-requests, so only IPv4 works with ARP on this platform.
76 78
79=head2 tincd/bsd
80
81TAP-device, maybe; migth work for many bsd variants.
82
83This driver is a newer version of the C<tincd/*bsd> drivers. It I<might>
84provide a TAP device, or might not work at all. You might try this
85interface type first, and, if it doesn't work, try one of the OS-specific
86drivers.
87
77=head2 tincd/freebsd 88=head2 tincd/freebsd
78 89
79TAP-device; part of the kernel (since 4.x, maybe earlier). 90TAP-device; part of the kernel (since 4.x, maybe earlier).
80 91
81C<ifname> should be set to the path of a tap device, 92C<ifname> should be set to the path of a tap device,
… …
156The interface MAC and MTU are I<NOT> set up for you. Please try it out and 167The interface MAC and MTU are I<NOT> set up for you. Please try it out and
157send me an C<ifconfig> command invocation that does that. 168send me an C<ifconfig> command invocation that does that.
158 169
159See C<tincd/netbsd> for more information. 170See C<tincd/netbsd> for more information.
160 171
161Completely unstested so far. 172Completely untested so far.
162 173
163=head2 tincd/mingw 174=head2 tincd/mingw
164 175
165TAP-device; see C<native/cygwin> for more information. 176TAP-device; see C<native/cygwin> for more information.
166 177
… …
177 188
178Completely untested so far. 189Completely untested so far.
179 190
180=head2 tincd/uml_socket 191=head2 tincd/uml_socket
181 192
182TAP-device; purpose unknown and untested, probably creates a unix datagram 193TAP-device; purpose unknown and untested, probably creates a UNIX datagram
183socket (path given by C<ifname>) and reads and writes raw packets, so 194socket (path given by C<ifname>) and reads and writes raw packets, so
184might be useful in other than UML contexts. 195might be useful in other than UML contexts.
185 196
186No network interface is created, and the MAC and MTU must be set as 197No network interface is created, and the MAC and MTU must be set as
187approriate on the other side of the socket. GVPE will exit if the MAC 198appropriate on the other side of the socket. GVPE will exit if the MAC
188address doesn't match what it expects. 199address doesn't match what it expects.
189 200
190Completely untested so far. 201Completely untested so far.
191 202
192=head2 tincd/cygwin 203=head2 tincd/cygwin
… …
197 208
198gvpe(5). 209gvpe(5).
199 210
200=head1 AUTHOR 211=head1 AUTHOR
201 212
202Marc Lehmann <gvpe@plan9.de> 213Marc Lehmann <gvpe@schmorp.de>
203 214

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines