vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| redmar wrote: >>>I've successfully added the tap device with these files to my 3.3 > > > stable box, > >>Why do people need this device? Isn't it the same as tun(4)? > > > tun is network layer, tap is datalink layer. > I'm for example using the tap device for a bridged VPN with OpenVPN. > Quoting the gif(4) man page, "... Finally, the gif interface may be used as a bridge(4) member. Ethernet frames forwarded by the bridge to the gif interface are encapsulated in-side an IPv4 or IPv6 header (depending on how the interface is configured), with transport protocol number 97 (etherip). IPv4 or IPv6 packets carrying transport protocol 97 are delivered to the gif interface whose "physical" addresses match the source/destination addresses of the packet (the source address of the packet must match the destination "physical" address, and vice versa). ...." So what's the adventage of this tun/tap driver? |
| Thread Tools | |
| Display Modes | |
|
|