… | |
… | |
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 | |
128 | |
102 | A newer (and reportedly much more stable) driver that also supports TAP |
129 | The driver must be loaded before use: |
103 | operations is available here: |
|
|
104 | |
130 | |
105 | http://www-user.rhrk.uni-kl.de/~nissler/tuntap/ |
131 | kmodload tunnel |
106 | |
|
|
107 | But GVPE has not been used with it, and has not been ported to it's TAP |
|
|
108 | interface. Patches are welcome. |
|
|
109 | |
132 | |
110 | =head2 tincd/solaris |
133 | =head2 tincd/solaris |
111 | |
134 | |
112 | TUN-device; already part of the kernel. see C<tincd/netbsd> for more |
135 | TUN-device; already part of the kernel(?), or available here: |
|
|
136 | |
|
|
137 | http://vtun.sourceforge.net/tun/ |
|
|
138 | |
|
|
139 | Some precompiled tun drivers might be available here: |
|
|
140 | |
|
|
141 | http://www.monkey.org/~dugsong/fragroute/ |
|
|
142 | |
|
|
143 | See C<tincd/netbsd> for more information. |
|
|
144 | |
113 | information. Completely untested so far. |
145 | Completely unstested so far. |
114 | |
146 | |
115 | =head2 tincd/mingw |
147 | =head2 tincd/mingw |
116 | |
148 | |
117 | TAP-device; see C<native/cygwin> for more information. Completey untested so far. |
149 | TAP-device; see C<native/cygwin> for more information. |
|
|
150 | |
|
|
151 | Completely untested so far. |
|
|
152 | |
|
|
153 | =head2 tincd/raw_socket |
|
|
154 | |
|
|
155 | TAP-device; purpose unknown and untested, probably binds itself on an |
|
|
156 | existing ethernet device (given by C<ifname>), which should probably not |
|
|
157 | be configured in any way, except for setting it I<up>. |
|
|
158 | |
|
|
159 | =head2 tincd/uml_socket |
|
|
160 | |
|
|
161 | TAP-device; purpose unknown and untested, probably creates a unix datagram |
|
|
162 | socket (path given by C<ifname>) and reads and writes raw packets, so |
|
|
163 | might be useful in other than UML contexts. |
118 | |
164 | |
119 | =head2 tincd/cygwin |
165 | =head2 tincd/cygwin |
120 | |
166 | |
121 | Known to be broken. |
167 | Known to be broken, use C<native/cygwin> instead. |
122 | |
|
|
123 | |
168 | |
124 | =head1 SEE ALSO |
169 | =head1 SEE ALSO |
125 | |
170 | |
126 | gvpe(5). |
171 | gvpe(5). |
127 | |
172 | |