Re: I'm experiencing a collision between the Vagrant VMware plugin and the cisco vpn anyconnect client. Does anyone have a workaround for this?

[Trevor Roberts]

Does your work network possibly use the same subnet as one of your vmnet's?  If so, consider changing the Fusion network settings.

I have not had any problems with Cisco AnyConnect on my system.

On Friday, May 17, 2013 12:53:31 PM UTC-7, Dave Casey wrote:

I haven't had any issues with VMware fusion competing with the vpn client, and I don't appear to have any problems with vagrant-virtualbox competing with the vpn client, but if I vagrant up with the vmware provider, it hangs until I disconnect my vpn connection.

Any suggestions?

Thanks,

-Dave

[Dave Casey]

The message I get:

The VMware network device 'vmnet1' can't be started because

its routes collide with another device: 'utun0'. Please

either fix the settings of the VMware network device or stop the

colliding device. Your machine can't be started while VMware

networking is broken.

ifconfig:

utun0: flags=80d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1406

inet 10.48.17.225 --> 10.48.17.225 netmask 0xfffff000 

vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 00:50:56:c0:00:01 

inet 172.16.243.1 netmask 0xffffff00 broadcast 172.16.243.255

[Glen Zangirolami]

A subnet in your vmnet is conflicting with a subnet in your VPN connection. Changing that value depends on if you are using OSX, Windows, or Linux. See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003463 to change the subnet for Fusion 3+

[Karel]

I'm experiencing the same problem. Have you solved it? The links seems dead.

I'm really not a network expert so some explanations would be welcome. Thanks

[Karel]

Here are some details. I tried different IP for my host only (10.0.0.x, 192.168.x.x). 

The error message:

The host only network with the IP '10.0.0.10' would collide with
another device 'tun0'. This means that VMware cannot create
a proper networking device to route to your VM. Please choose
another IP or shut down the existing device.

The device in question:

tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.14.1.13 --> 10.14.1.13 netmask 0xffff0000 
open (pid 928)

[Bryan Bishop]

I'm on OSX Mavericks and I saw this issue too.  I have had success using Homebrew's openconnect VPN instead of the official Cisco client.  The openconnect VPN works great and I was able to spin up vagrant machines while connected to the vpn, and the VM's also had access to the VPN network too. 

[Karel Ledru-Mathé]

Sorry for the late answer, I was off the grid for a while.

I haven't solved my problem. I'm not sure how I can reconfigure the chef box and I had no luck with openconnect. I also tried Viscosity with the same problem.

--
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/cUyiC1Ipfgg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.