On 5/26/2015 10:26 AM, dragon788 wrote:
Your forwarding won't get put in place UNLESS you use the Vagrant up command. Vagrant does some behind the scenes magic to add the port forwarding and restart the NAT networking services before/while it brings the box up.If you try 'VAGRANT_LOG=debug vagrant up' and then examine the output does it give more details about why it fails? On Monday, May 25, 2015 at 9:16:28 AM UTC-5, Robert Dailey wrote: I am using VirtualBox and Ubuntu/Trusty32. I ran the following to setup my VM: $ vagrant box add ubuntu/trusty32 $ vagrant init ubunty/trusty32 $ vagrant up I did modify my Vagrantfile a bit, since DNS resolution wasn't working in the guest through NAT network mode. I've attached my Vagrantfile and logs showing the TCP port forward failure for port 22: 00:00:00.973356 NAT: set redirect TCP host 0.0.0.0:2222 <http://0.0.0.0:2222> => guest 10.0.2.15:22 <http://10.0.2.15:22> 00:00:00.973441 NAT: failed to redirect TCP 0.0.0.0:2222 <http://0.0.0.0:2222> => 10.0.2.15:22 <http://10.0.2.15:22> Note in my test, I am launching the VM directly from VirtualBox and not through the 'vagrant' command. However both yield the same results. Anyone know how to fix this issue? -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout.
I will give this a try. Is there a reason why I needed to specify the DNS resolution settings in order to get DNS working using NAT? It seems like it should "just work", no further configuration required. Any advice on that? -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
