Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Vagrant VMware provider with Cisco AnyConnect VPN tunneling all #5740
Re-opening an old issue that is still a problem. Many have posted none have solved this one.
Using the vagrant vmware provider while VPN'd into a network using Cisco AnyConnect, I receive the folllowing error from vagrant up:
The VMware network device 'vmnet1' can't be started because
Routing to the IP '[IP address]' should route through 'vmnet1', but
I've tried "Enable local LAN access' in the anyconnect client. It allowed the setting; however, it didn't make a difference. Has anyone elese encountered this issue?
referenced this issue
Jul 7, 2015
I just hit this today as well.
When the AnyConnect VPN is connected, I get a similar error as above:
However, if I
*** Now connect the VPN ***
It appears that the only thing that doesn't work when the VPN is active is the initial
If I start a VM in Fusion manually, Fusion has no problem configuring the network adapters correctly while the VPN is active, and NAT works perfectly fine from the VM. It seems like the only thing preventing
@mitchellh is there any configuration option we can add to the Vagrantfile to force Vagrant to skip the "Verifying vmnet devices are healthy..." step?
(FYI, I had to upgrade to Vagrant 2.0.1 and vagrant-vmware-fusion 5.0.3 for the