The driver is used by other popular software so it looks like it is here to stay. It is implemented as part of the Linux Kernel. Go here Tun TAP driver for MAC OS X and download the installer package for Leopard. Extract the package using Stuffit Expander (free app, google for it), and this will create a pkg file. The following legacy packages can be used with previous Mac OS X versions. These reflect old versions current at the time of the respective Mac OS X versions. Since the base functionality provided by TunTap hasn't changed significantly over the years, these are mostly equivalent feature-wise. Version 20050515 for Mac OS X 10.3 (Panther). FreeBSD ships with the TUN/TAP driver, and the device nodes for tap0, tap1, tap2, tap3, tun0, tun1, tun2 and tun3 are made by default. However, only the TUN driver is linked into the GENERIC kernel. To load the TAP driver, enter: kldload iftap: See man rc(8) to find out how you can do this at boot time.
In computer networking, TUN and TAP are kernelvirtual network devices. Being network devices supported entirely in software, they differ from ordinary network devices which are backed by physical network adapters.
The Universal TUN/TAP Driver originated in 2000 as a merger of the corresponding drivers in Solaris, Linux and BSD.[1] The driver continues to be maintained as part of the Linux[2] and FreeBSD[3][4] kernels.
Design[edit]
Though both for tunneling purposes, TUN and TAP can't be used together because they transmit and receive packets at different layers of the network stack. TUN, namely network TUNnel, simulates a network layer device and operates in layer 3 carrying IP packets. TAP, namely network TAP, simulates a link layer device and operates in layer 2 carrying Ethernet frames. TUN is used with routing. TAP can be used to create a user spacenetwork bridge.[2]
Packets sent by an operating system via a TUN/TAP device are delivered to a user space program which attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case the TUN/TAP device delivers (or 'injects') these packets to the operating-system network stack thus emulating their reception from an external source.[2]
Applications[edit]
- Virtual private networks
- OpenVPN, Ethernet/IP over TCP/UDP; encrypted, compressed
- ZeroTier, Ethernet/IP over TCP/UDP; encrypted, compressed, cryptographic addressing scheme
- FreeLAN, open-source, free, multi-platform IPv4, IPv6 and peer-to-peer VPN software over UDP/IP.
- n2n, an open source Layer 2 over Layer 3 VPN application which uses a peer-to-peer architecture for network membership and routing
- Tinc, Ethernet/IPv4/IPv6 over TCP/UDP; encrypted, compressed
- VTun, Ethernet/IP/serial/Unix pipe over TCP; encrypted, compressed, traffic-shaping
- coLinux, Ethernet/IP over TCP/UDP
- Virtual-machine networking
- QEMU/KVM
- Connecting real machines with network simulation
- ns-3[5]
- NAT
Tun Tap Driver For Mac Os X 10.10
- TAYGA, a stateless NAT64 implementation for Linux
Platforms[edit]
Platforms with TUN/TAP drivers include:
- Linux, starting around version 2.1.60 of the Linux kernel mainline
- iOS (tun driver only)
- OS X (native support only for TUN (utun))[6]
- Android[7]
- Windows 2000/XP/Vista/7/8/8.1/10
See also[edit]
Tun/tap Driver For Mac Os X
References[edit]
Tun Tap Driver For Mac Os X 64
- ^'Universal TUN/TAP driver'. VTun project on SourceForge. Retrieved 2019-07-12.
- ^ abc'Universal TUN/TAP device driver'. Linux kernel. Retrieved 2020-08-17.
- ^'TUN(4) manual page'. FreeBSD. Retrieved 2019-07-12.
- ^'TAP(4) manual page'. FreeBSD. Retrieved 2019-07-12.
- ^'ns3::TapBridge Class Reference'. nsnam.org. Retrieved 2019-03-28.
- ^Back to My Mac uses an IPv6 tunnel on device utun0.
- ^'de.schaeuffelhut.android.openvpn'. F-Droid. 2013-01-10. Retrieved 2019-03-28.
Comments are closed.