vagrant box build using VirtualBox - oracle linux 7 internal network cannot communicate with other internal network outside of the vagrant boxes built

[K]

I did write a summary but it got longer and longer.

So, I will try to be direct, even if it sounds stupid.

I'm new to Vagrant.

After a Vagrant Linux box is built and up and running inside VirtualBox, does Vagrant have any kind of, lets say, 'firewall' around the boxes network that makes the VMs from Vagrant different from the VMs built straight in VirtualBox by hand ?

Or , once created in VirtualBox - they are independent in the way they run ( ie have left the Vagrant 'system of operation' behind ) with regards networking.

Im really getting desperate to ask such an apparently idiotic question believe me.

I don't want to drag people into a network discussion. Im just trying to binary chop the issue so I can see whether I can ignore Vagrant at this stage.

.

[Alvaro Miranda Aguilera]

hello

vagrant by default will create the new VMS NAT only, so the VMs have access to your host and from there what your host can reach,

if you have multiple vms, the IP is nat only so it shoulnt allow you contact between them.

If you have VMS managed out of vagrant, you should be able to access them if you are using any networking other than NAT,

alvaro 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/21251489-1d9e-4b3d-a6ab-793d959b5d3a%40googlegroups.com.

--

Alvaro