|Authors||Anil Madhavapeddy <email@example.com>, David Scott <firstname.lastname@example.org>, David Sheets <email@example.com>, Gaetan de Villele <firstname.lastname@example.org>, Ian Campbell <email@example.com>, Magnus Skjegstad <firstname.lastname@example.org>, Mindy Preston <email@example.com>, Sebastiaan van Stijn <firstname.lastname@example.org>, Thomas Gazagnaire <email@example.com> and Thomas Leonard <firstname.lastname@example.org>|
|Maintainer||David Scott <email@example.com>|
|Published||Nov 24, 2016|
|Statistics||Installed 13times in last month.|
VPN-friendly networking devices for [HyperKit](https://github.com/docker/hyperkit)
Running a VM usually involves modifying the network configuration on the host, for example by activating Ethernet bridges, new routing table entries, DNS and firewall/NAT configurations. Activating a VPN involves modifying the same routing tables, DNS and firewall/NAT configurations and therefore there can be a clash -- this often results in the network connection to the VM being disconnected.
VPNKit, part of HyperKit attempts to work nicely with VPN software by intercepting the VM traffic at the Ethernet level, parsing and understanding protocols like NTP, DNS, UDP, TCP and doing the "right thing" with respect to the host's VPN configuration.
VPNKit operates by reconstructing Ethernet traffic from the VM and translating it into the relevant socket API calls on OSX or Windows. This allows the host application to generate traffic without requiring low-level Ethernet bridging support.
|No package is dependent|