VirtualBox resets VPNs

[dispmaxstaff]

I have 3 VPNs from the host to outside, virtualbox has a guest with 1 NIC (NAT).
Seems like any network activity on guest causes host VPNs to be reset (disconnect).
Without VPNs all network functionality seems to work as intended.
This was the case with 2.x vbox and 3.x has the same problem too.
Did anyone have the same problem?

[kmansj]

I'm having something similar. I'm running Win7 Utlimate 64; after some amount of time (i.e., overnight), my network can't connect. Windows says there's no network functionality, and it seems to be connected to the Host-only networking controller or something. After a repair, my normal network comes back, but VPN is dead.

-Kman

[vbox4me2]

Known issue, use Bridge for the Guests if the Host needs vpn. (same the other way around)

[dispmaxstaff]

Known issue, use Bridge for the Guests if the Host needs vpn. (same the other way around)

Thanks for the reply. The problem is that I need VMs to have the access to VPN subnets too like host does.
Is there any open bug ticket for this? Do you think if I'll create ticket this issue will be fixed?

[BillG]

That usually doesn't work. Nothing to do with VirtualBox.

A VPN is a point to point link. The remote server you connect to only has a host route back to the VPN client through the tunnel. For that reason you cannot just connect another machine to the VPN host and use the connection. The packet might reach the remote server but that server has no way to route the reply. It only knows about the actual VPN client.

To allow more than one machine to use a VPN connection you need to set up a site to site (also called router to router or LAN to LAN) VPN connction, not a simple client-server type VPN.

[dispmaxstaff]

Dear BillG,
This configuration works perfectly fine with VMware NAT and few route adds and has been working for years. I don't need help with routing and NAT, thank you.
The only problem I have is that vbox resets VPNs, that's all.

[dispmaxstaff]

This is annoying bug and the only reason that prevents me from using vbox instead of vmware. Is there any chance it's fixed?