C:\Users\Bran\Sites\dvagrant>vagrant up
Host only networking is currently broken on Windows due to a bug
in jruby-win32ole. When the bug is fixed, a patch release for Vagrant
will be released to remove this error. Until then, please just use
forwarded ports.

Is there a way to use NAT or bridged networking instead?

Comments

branana’s picture

branana commented
Category: bug » support

I figured out if not specified in dvagrant's Vagrantfile, the "vagrant up" command will create a VM using NAT as the network adapter. I can specify it to be using bridged networking in order for it to be accessible to my Windows machine since Host-only networking is not available to me. http://vagrantup.com/docs/bridged_networking.html

I've tried destroying the VM and modifying the Vagrantfile with "config.vm.network :bridged", it still gives me an error about not being to call the private method "split".

My question is, do I run the VM with both NAT (for the SSH porforward, port 2222 to 22 so vagrant can manipulate the VM still) and enable bridged networking as well so that I can modify my HOSTS file to be able to access Apache in my browser on port 80?

branana’s picture

branana commented
Status: Active » Fixed

Nevermind, the answer is you don't need bridged or host-only networking. Just make sure you comment out every line related to networking in the Vagrantfile of this project and use NAT and forward the guest VM's port 80 to your host machine's port 80. That would allow you to reach Varnish through your host machine's web browser.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.