Cant communicate to Vbox VMs after VPN

[tman-kc]

I have some virtualbox VMs setup on a MAC OS X host. Each VM has two network interfaces, a NAT and a host only.
vm1 is 192.168.33.9
vm2 is 192.168.33.10
The localhost machine (the Mac) can ping both of these VMs, and each VM can ping one another.

After I connect to our VPN using the Cisco anyconnect client, the vpns can still ping one another. However, I am unable to ping the VM's by IP from the Mac. I suspect I need to add a route, but not sure what route to add.

Here is netstat -rn output from the MAC (localhost) prior to the VPN

192.168.33 link#13 UC 3 0 vboxnet
192.168.33.10 8:0:27:6e:db:af UHLWI 0 2 vboxnet 1154
192.168.33.255 ff:ff:ff:ff:ff:ff UHLWbI 0 1 vboxnet

And here is after the VPN connection is active
192.168.33.9 utun1 UHW3I 0 10 utun1 1437
192.168.33.10 utun1 UHW3I 0 4 utun1 1437
192.168.33.255 utun1 UHW3I 0 53 utun1 1566

Any help is appreciated, thank you.

[noteirak]

You would simply add a route to the host-only subnet you've configure (I guess 192.168.33.0/24?) to the host IP on the host-only interface. I do not have a mac so I can't tell you the command but under Linux it would go like this :

Code: Select all

ip route add 192.168.33.0/24 dev vboxnet0

Be aware that Cisco VPN client can a watchdog on the routing table and dynamically remove such entries that are not acknowledged, if route control is enforced by the VPN server.

[ChipMcK]

I do not have a mac

[Perryg]

I do not have a mac

In other posts you stated that you have 10.5 installed.
One example, Status of OSX on OSX

And just what am I supposed to see? I don't see where noteirak posted to that topic at all.

[ChipMcK]

ooops i cant tell one from the other

[Perryg]

Been there,.. done that.

[frank]

This was most likely a bug in the Cisco AnyConnect software. We've got a pointer to a version which fixed the problem, see version 3.1.08009 of this software.

[frank]

Sorry, just saw that the download requires special permissions...

[klaus]

Any Cisco AnyConnect user should know (or be able to find out) who in his organization has access to the Cisco download page... this is pretty much all we could do, pushing them to fix the problem. We can't provide the file for all to download.

[nob13]

In case anybody still needs an intermediate solution for this. You can fix up the broken route by:

Code: Select all

route add -net 192.168.56.0/24 -interface vboxnet0

where 192.168.56.0/24 is your host only network IP range, and vboxnet0 is the name of the virtual network, as in the VirtualBox preference dialog.

[watsoncj]

I unchecked the "Block connections to untrusted servers" box and it seems to have resolved connectivity issue.