Hello, That's how vagrant work by default. Eth0 will be nat.
You need to add a private or public network, and use that for cluster communication. http://docs.vagrantup.com/v2/networking/private_network.html http://docs.vagrantup.com/v2/networking/public_network.html Alvaro. On Fri, Feb 27, 2015 at 8:18 AM, Victor L <[email protected]> wrote: > Hello, > I run vagrant/coreos on VirtualBox, so i am not sure if this is more > relevant to Vagrant, or to VirtualBox.... > On CoreOS nodes I have eth0 interface to show up as NAT in VirtualBox > network settings and have the same ip (10.0.2.15) > for every node in cluster. Where's this network coming from (and for)? Is it > some VirtualBox-specific thing for internal management? > Thanks > > > -- > 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.
