… | |
… | |
74 | TAP-device; part of the kernel (since 4.x, maybe earlier). To initialize |
74 | TAP-device; part of the kernel (since 4.x, maybe earlier). To initialize |
75 | the interface, use this command: |
75 | the interface, use this command: |
76 | |
76 | |
77 | ifconfig $IFNAME ether $MAC mtu $MTU up |
77 | ifconfig $IFNAME ether $MAC mtu $MTU up |
78 | |
78 | |
|
|
79 | These commands might be helpful examples: |
|
|
80 | |
|
|
81 | ifconfig $IFNAME 10.0.0.$NODEID |
|
|
82 | route add -net 10.0.0.0 -netmask 255.255.255.0 -interface $IFNAME 10.0.0.$NODEID |
|
|
83 | |
79 | =head2 tincd/netbsd |
84 | =head2 tincd/netbsd |
80 | |
85 | |
81 | TUN-device; The interface is a point to point-device. To initialize it, |
86 | TUN-device; The interface is a point to point-device. To initialize it, |
82 | you currently need to configure it as such, giving it an address on your |
87 | you currently need to configure it as such, giving it an address on your |
83 | vpn (the exact address doesn't matter), like this: |
88 | vpn (the exact address doesn't matter), like this: |
… | |
… | |
89 | |
94 | |
90 | =head2 tincd/openbsd |
95 | =head2 tincd/openbsd |
91 | |
96 | |
92 | TUN-device; already part of the kernel. See C<tincd/netbsd> for more information. |
97 | TUN-device; already part of the kernel. See C<tincd/netbsd> for more information. |
93 | |
98 | |
|
|
99 | =head2 native/darwin |
|
|
100 | |
|
|
101 | TAP-device; |
|
|
102 | |
|
|
103 | The necessary kernel extension can be found here: |
|
|
104 | |
|
|
105 | http://www-user.rhrk.uni-kl.de/~nissler/tuntap/ |
|
|
106 | |
|
|
107 | There are two drivers, the one to use is the "tap" driver. It driver must |
|
|
108 | be loaded before use, read the docs on how to install it as a startup |
|
|
109 | item. |
|
|
110 | |
|
|
111 | To initialize the interface, use this command: |
|
|
112 | |
|
|
113 | ifconfig $IFNAME ether $MAC mtu $MTU up |
|
|
114 | |
|
|
115 | These commands might be helpful examples: |
|
|
116 | |
|
|
117 | ifconfig $IFNAME 10.0.0.$NODEID |
|
|
118 | route add -net 10.0.0.0 -interface $IFNAME 255.255.255.0 |
|
|
119 | |
94 | =head2 tincd/darwin |
120 | =head2 tincd/darwin |
95 | |
121 | |
96 | TUN-device; See C<tincd/netbsd> for more information. |
122 | TUN-device; See C<tincd/netbsd> for more information. C<native/darwin> is |
|
|
123 | preferable. |
97 | |
124 | |
98 | The necessary kernel extension can be found here: |
125 | The necessary kernel extension can be found here: |
99 | |
126 | |
100 | http://chrisp.de/en/projects/tunnel.html |
127 | http://chrisp.de/en/projects/tunnel.html |
101 | |
|
|
102 | A newer (and reportedly much more stable) driver that also supports TAP |
|
|
103 | operations is available here: |
|
|
104 | |
|
|
105 | http://www-user.rhrk.uni-kl.de/~nissler/tuntap/ |
|
|
106 | |
|
|
107 | But GVPE has not been ported to it's TAP interface. Patches are welcome. |
|
|
108 | |
128 | |
109 | The driver must be loaded before use: |
129 | The driver must be loaded before use: |
110 | |
130 | |
111 | kmodload tunnel |
131 | kmodload tunnel |
112 | |
132 | |
113 | =head2 tincd/solaris |
133 | =head2 tincd/solaris |
114 | |
134 | |
115 | TUN-device; already part of the kernel, or available here: |
135 | TUN-device; already part of the kernel(?), or available here: |
116 | |
136 | |
117 | http://vtun.sourceforge.net/tun/ |
137 | http://vtun.sourceforge.net/tun/ |
118 | |
138 | |
119 | Some precompiled tun drivers might be available here: |
139 | Some precompiled tun drivers might be available here: |
120 | |
140 | |