I use a VPN to connect my Mac to my employer's network, and run our standard developer environment in Virtualbox. I need to use Bridged networking, and everything works apart from when I configure the network interface that the VM should use, I only get options for en0 (ethernet) and en1 (airport), and if I choose either of those the VM bypasses the VPN.
Provided that I start Virtualbox after bringing the VPN up, the tun0 interface should also show up in that list, which would make it Do The Right Thing. But it doesn't. Please implement this in the next release, I can't imagine that it would be difficult.
Persuading VMs to use a VPN
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Persuading VMs to use a VPN
VPN connections are point to point connections. They are an emulation of a cable connection between host and guest. They cannot be shared or routed.
If you want to connect to your employer's network from the vm, use bridged networking and create the VPN connection from the guest.
If you want to connect to your employer's network from the vm, use bridged networking and create the VPN connection from the guest.
Bill