does VMware NAT and Vagrant allow for multi-VM communication on adapter1?

[rus...@infinite.io]

In the case of Virtualbox I use 'natnetwork' to allow NAT and communication across multi-cluster setup, However Vagrant only allows adapter1 to be NAT.  Virtual box NAT doesn't allow multi-cluster communication. So I'm dropping Virtualbox and trying VMware.  Before I have to purchase a VMware license for the plugin to work in Vagrant, will Vagrant and VMware allow NAT to the outside and multi-VM communication on adapter1?

Thanks!

[Alvaro Miranda Aguilera]

Hello,

Ignore nic one one Virtualbox for a second and do a diagram using private networks.

If you have 2 separate clusters, then you need:

a. On first cluster a nic for that cluster interconnect, say 10.11.11.x

b. On second cluster a nic for that cluster itnerconnect, say 10.12.12.x

then, How each cluster see each other?

a. on both cluster you can add a known interface, say 10.10.10.10

OR

b. On each cluster, you choose one node, you add a common interface, and then that become the GW/Router for that network, etc

is same as having physical clusters

I think the easiest is just add 2 private network to each node if thats what you are after.

A diagram will help a lot if you can express what you are after.

Alvaro.

On Wed, Jul 27, 2016 at 12:12 PM, <rus...@infinite.io> wrote:

In the case of Virtualbox I use 'natnetwork' to allow NAT and communication across multi-cluster setup, However Vagrant only allows adapter1 to be NAT.  Virtual box NAT doesn't allow multi-cluster communication. So I'm dropping Virtualbox and trying VMware.  Before I have to purchase a VMware license for the plugin to work in Vagrant, will Vagrant and VMware allow NAT to the outside and multi-VM communication on adapter1?

Thanks!

--
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/c2a3f7d7-3775-47cd-b84d-168f12d040c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rus...@infinite.io]

Thanks for you answer.  Yes I did consider a private network for VM <-> VM comm, however I'm trying to simulate a hardware setup where the same software runs on the VM and hardware so I would like to keep the interfaces, etc., the same and not have special case for VM.  Multi-Cluster was a bad term for me to use, i really mean a cluster of VMs.  

I have this  all working with Virtualbox alone, it's when I add Vagrant into the mix that I run into problems because Vagrant requires  adapter1 to be NAT not NATNETWORK.  I believe VMware's NAT is different from Virtualbox in that it allows VM<->VM communication and to the outside.   I would just like to know if this is true before I spend $80 for Vagrant VMware license and then $250 for VMware Workstation.  See attachment.

[Alvaro Miranda Aguilera]

Hello,

You can add a 2nd interface to Virtualbox and configure it like you want, just ignore the first interface.

You can use custom commands to configure them, just take into consideration that all the manual work to do this, may be overkill, so, you could either, use normal private network, or do the extra step and use the NAT<something> you require.

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/09913e6d-2886-47f1-a190-c05f5d808699%40googlegroups.com.

[rus...@infinite.io]

So the answer is Yes.  Since i posted the question i've bought vmware workstation and the plugin.  VM <-> VM over NAT works with VMware (not virutalbox)

On Tuesday, July 26, 2016 at 7:12:25 PM UTC-5, rus...@infinite.io wrote: