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.2 by pcg, Thu Jan 27 07:04:51 2005 UTC vs.
Revision 1.6 by pcg, Wed Mar 23 17:03:58 2005 UTC

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 native/linux 33=head2 native/linux
34 34
35TAP-device is already part of the kernel (only 2.4 supported, but see 35TAP-device; already part of the kernel (only 2.4+ supported, but see
36tincd/linux). This is the configuration tested best, as gvpe is being 36tincd/linux). This is the configuration tested best, as gvpe is being
37developed on this platform. 37developed on this platform.
38 38
39To configure the interface, use either iproute2: 39To configure the interface, use either iproute2:
40 40
41 ip set $IFNAME address $MAC mtu $MTU up 41 ip set $IFNAME address $MAC mtu $MTU up
42 ip addr add $IFNAME 10.11.12.13 42 ip addr add $IFNAME 10.11.12.13
43 ip route add $IFNAME 10.11.12.13/8 43 ip route add $IFNAME 10.11.12.13/8
44 44
45Or ifconfig: 45Or C<ifconfig>:
46 46
47 ifconfig $IFNAME hw ether $MAC mtu $MTU 47 ifconfig $IFNAME hw ether $MAC mtu $MTU
48 ifconfig $IFNAME 10.11.12.13 netmask 255.0.0.0 48 ifconfig $IFNAME 10.11.12.13 netmask 255.0.0.0
49 49
50To hardwire ARP addresses, use iproute2 (ifconfig can do it, too): 50To hardwire ARP addresses, use iproute2 (C<arp> can do it, too):
51 51
52 MAC=fe:fd:80:00:00:$(printf "%02x" $NODEID) 52 MAC=fe:fd:80:00:00:$(printf "%02x" $NODEID)
53 ip neighbour add 10.11.12.13 lladdr $MAC nud permanent dev $IFNAME 53 ip neighbour add 10.11.12.13 lladdr $MAC nud permanent dev $IFNAME
54 54
55=head2 tincd/linux 55=head2 tincd/linux
56 56
57TAP-device is already part of the kernel (2.2 and 2.4 supported, only 2.4 57TAP-device; already part of the kernel (2.2+ supported). See
58tested). See C<native/linux> for more info. 58C<native/linux> for more info.
59 59
60=head2 native/cygwin 60=head2 native/cygwin
61 61
62TAP-device. The MAC need not be set (and in fact I<cannot> be set). The 62TAP-device; The TAP device to be used must either be the CIPE driver
63MAC address is dynamically being patched into packets and ARP-requests, so 63(C<http://cipe-win32.sourceforge.net/>), or (highly recommended) the newer
64only IPv4 works with ARP on this platform. 64TAP-Win32 driver bundled with openvpn (http://openvpn.sf.net/). Just
65download and run the openvpn installer. The only option you need to select
66is the TAP driver.
65 67
66The TAP device to be used must either be the CIPE driver 68The MAC need not be set (and in fact I<cannot> be set). The MAC address
67(C<http://cipe-win32.sourceforge.net/>), or the newer TAP-Win32 driver 69is dynamically being patched into packets and ARP-requests, so only IPv4
68bundled with openvpn (http://openvpn.sf.net/). Just download and run the 70works with ARP on this platform.
69openvpn installer. The only option you need to select is the TAP driver.
70 71
71=head2 tincd/freebsd 72=head2 tincd/freebsd
72 73
73TAP-device is part of kernel (since 4.x, maybe earlier). To initialize the 74TAP-device; part of the kernel (since 4.x, maybe earlier). To initialize
74interface, use this command: 75the interface, use this command:
75 76
76 ifconfig $IFNAME ether $MAC mtu $MTU up 77 ifconfig $IFNAME ether $MAC mtu $MTU up
77 78
78=head2 tincd/netbsd 79=head2 tincd/netbsd
79 80
80TUN-device. The interface is a point to point-device. To initialize it, 81TUN-device; The interface is a point to point-device. To initialize it,
81you currently need to configure it as such, giving it an address on your 82you currently need to configure it as such, giving it an address on your
82vpn (the exact address doesn't matter), like this: 83vpn (the exact address doesn't matter), like this:
83 84
84 ifconfig $IFNAME mtu $MTU up 85 ifconfig $IFNAME mtu $MTU up
85 ifconfig $IFNAME 10.11.12.13 10.55.66.77 86 ifconfig $IFNAME 10.11.12.13 10.55.66.77
86 route add -net 10.0.0.0 10.55.66.77 255.0.0.0 87 route add -net 10.0.0.0 10.55.66.77 255.0.0.0
87 ping -c1 10.55.66.77 # ping once to tell gvpe your gw ip 88 ping -c1 10.55.66.77 # ping once to tell gvpe your gw ip
88 89
89=head2 tincd/openbsd 90=head2 tincd/openbsd
90 91
91TUN-device is already part of the kernel. See C<tincd/netbsd> for more information. 92TUN-device; already part of the kernel. See C<tincd/netbsd> for more information.
93
94=head2 native/darwin
95
96TAP-device;
97
98The necessary kernel extension can be found here:
99
100 http://www-user.rhrk.uni-kl.de/~nissler/tuntap/
101
102There are two drivers, the one to use is the "tap" driver. It driver must
103be loaded before use, using C<kmodload>.
92 104
93=head2 tincd/darwin 105=head2 tincd/darwin
94 106
95TUN-device. See C<tincd/netbsd> for more information. 107TUN-device; See C<tincd/netbsd> for more information. C<native/darwin> is
108preferable.
96 109
97The necessary kernel extension can be found here: 110The necessary kernel extension can be found here:
98 111
99 http://chrisp.de/en/projects/tunnel.html 112 http://chrisp.de/en/projects/tunnel.html
100 113
114The driver must be loaded before use:
115
116 kmodload tunnel
117
101=head2 tincd/solaris 118=head2 tincd/solaris
102 119
103TUN-device is already part of the kernel. see C<tincd/netbsd> for more information. Completey untested so far. 120TUN-device; already part of the kernel, or available here:
121
122 http://vtun.sourceforge.net/tun/
123
124Some precompiled tun drivers might be available here:
125
126 http://www.monkey.org/~dugsong/fragroute/
127
128See C<tincd/netbsd> for more information.
129
130Completely unstested so far.
104 131
105=head2 tincd/mingw 132=head2 tincd/mingw
106 133
107TAP-device, see C<native/cygwin> for more information. Completey untested so far. 134TAP-device; see C<native/cygwin> for more information.
135
136Completely untested so far.
137
138=head2 tincd/raw_socket
139
140TAP-device; purpose unknown and untested, probably binds itself on an
141existing ethernet device (given by C<ifname>), which should probably not
142be configured in any way, except for setting it I<up>.
143
144=head2 tincd/uml_socket
145
146TAP-device; purpose unknown and untested, probably creates a unix datagram
147socket (path given by C<ifname>) and reads and writes raw packets, so
148might be useful in other than UML contexts.
108 149
109=head2 tincd/cygwin 150=head2 tincd/cygwin
110 151
111Known to be broken. 152Known to be broken, use C<native/cygwin> instead.
112
113 153
114=head1 SEE ALSO 154=head1 SEE ALSO
115 155
116gvpe(5). 156gvpe(5).
117 157

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines