| … | |
… | |
| 9 | |
9 | |
| 10 | =head1 TUN vs. TAP interface |
10 | =head1 TUN vs. TAP interface |
| 11 | |
11 | |
| 12 | Most operating systems nowadays support something called a |
12 | Most operating systems nowadays support something called a |
| 13 | I<tunnel>-device, which makes it possible to divert IPv4 (and often other |
13 | I<tunnel>-device, which makes it possible to divert IPv4 (and often other |
| 14 | protocols, too) into a userspace daemon like C<gvpe>. This is being |
14 | protocols, too) into a user space daemon like C<gvpe>. This is being |
| 15 | referred to as a TUN-device. |
15 | referred to as a TUN-device. |
| 16 | |
16 | |
| 17 | This is fine for point-to-point tunnels, but for a virtual ethernet, an |
17 | This is fine for point-to-point tunnels, but for a virtual ethernet, an |
| 18 | additional ethernet header is needed. This functionality (called a TAP |
18 | additional ethernet header is needed. This functionality (called a TAP |
| 19 | device here) is only provided by a subset of the configurations. |
19 | device here) is only provided by a subset of the configurations. |
| … | |
… | |
| 167 | The interface MAC and MTU are I<NOT> set up for you. Please try it out and |
167 | The interface MAC and MTU are I<NOT> set up for you. Please try it out and |
| 168 | send me an C<ifconfig> command invocation that does that. |
168 | send me an C<ifconfig> command invocation that does that. |
| 169 | |
169 | |
| 170 | See C<tincd/netbsd> for more information. |
170 | See C<tincd/netbsd> for more information. |
| 171 | |
171 | |
| 172 | Completely unstested so far. |
172 | Completely untested so far. |
| 173 | |
173 | |
| 174 | =head2 tincd/mingw |
174 | =head2 tincd/mingw |
| 175 | |
175 | |
| 176 | TAP-device; see C<native/cygwin> for more information. |
176 | TAP-device; see C<native/cygwin> for more information. |
| 177 | |
177 | |
| … | |
… | |
| 188 | |
188 | |
| 189 | Completely untested so far. |
189 | Completely untested so far. |
| 190 | |
190 | |
| 191 | =head2 tincd/uml_socket |
191 | =head2 tincd/uml_socket |
| 192 | |
192 | |
| 193 | TAP-device; purpose unknown and untested, probably creates a unix datagram |
193 | TAP-device; purpose unknown and untested, probably creates a UNIX datagram |
| 194 | socket (path given by C<ifname>) and reads and writes raw packets, so |
194 | socket (path given by C<ifname>) and reads and writes raw packets, so |
| 195 | might be useful in other than UML contexts. |
195 | might be useful in other than UML contexts. |
| 196 | |
196 | |
| 197 | No network interface is created, and the MAC and MTU must be set as |
197 | No network interface is created, and the MAC and MTU must be set as |
| 198 | approriate on the other side of the socket. GVPE will exit if the MAC |
198 | appropriate on the other side of the socket. GVPE will exit if the MAC |
| 199 | address doesn't match what it expects. |
199 | address doesn't match what it expects. |
| 200 | |
200 | |
| 201 | Completely untested so far. |
201 | Completely untested so far. |
| 202 | |
202 | |
| 203 | =head2 tincd/cygwin |
203 | =head2 tincd/cygwin |
