the way vagrant works at the moment wont setup a router on the 2nd interface thats why you cant access it from the 2nd network
the vagrant way is configure port forwarding between the vagrant box guest and the host, then use host:port to access the guest application On Wed, Jul 30, 2014 at 3:34 AM, david duan <[email protected]> wrote: > Hi , I using vagrant 1.6.3 to import a appscale 2.0 official box on > virualbox 4.3. it works well. the host is windows server > 2008.(192.168.1.115) > > I set this vm in public network ,the dhcp, get the ip of > 192.168.1.117(bridged mode), it can access to the internet.and changing the > passwd. > > and using another vm of ubuntu 12.02(192.168.1.118) bridged mode , to > launch appscale (192.168.1.117). > > It works, But strange thing happens , *I notice the vm 192.168.1.117 can > only be accessed by the same network segment. meaning * > > *192.168.1.1 to 192.168.1.254 are ok. but other like 192.168.2.1 can not > ping and see the site in 192.168.1.117. 192.168.1.117 can ping 192.168.2.1 > and internet..... I am using bridged mode(public network) on vm .not the > nat or host only(private network).* > > *it is not the virtualbox issue, because I directly launch a vm( bridge > mode) on virtualbox without vagrant, it can be accessed by the other > network segment. * > > -- > 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. > -- 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.
