So in otherwords, vagrant isn't going to work correctly, or is there something else I can do to get my dev box, which is on a different subnet, to be able to connect/see the vagrant box?
On Thursday, May 15, 2014 7:39:44 PM UTC-4, Alvaro Miranda Aguilera wrote: > > Vagrant requires the first network to be nat, and connect over a forward > port to setup the vm. > > So you have a chicken egg, with no nat on eth0, vagrant can't connect to > the guest to setup the 2nd nic. > > Without the nat, vagrant will be able to only turn the guest on, and > shutdown force. > > Alvaro > > > On Fri, May 16, 2014 at 3:13 AM, synack <[email protected] > <javascript:>>wrote: > >> Hi All >> >> I'm trying to get a Bridge only setup going, no NAT. I've posted my >> question on superuser, but I thought I would post the link here for a bit >> more exposure as I'm really struggling to get this right. >> >> >> http://superuser.com/questions/752954/need-to-do-bridged-adapter-only-in-vagrant-no-nat/753563?noredirect=1#753563 >> >> Thanks for any help >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
