NatNetworking Query

[Shougeki]

Apologies if this is in the wron place, but I couldn't figure out where to put it.

I am pretty new to VBox but I have worked a lot with VMWare in the past. I am currently trying to set up a home network, and seem to be having some troubles with the networking.

My requirements are:
A number of machines on a network, all being able to talk to each other on various ports, including SSH. All CENTOS7 minimal.
Machines must not be able to talk or chatter on the hosts own network.
Machines need access to the inernet for updates etc. Via a proxy on this network or so forth would be fine.
Host machine needs to be able to ssh to the machines in the network, or at least one of them as a "jump" point.

I have three VMs set up, using NATNetwork, on a set of static IPs.
These machines have access out to the internet using the host as a gateway.
I see no apparant network chatter.
The machines cannot talk to each other. This seems to be my big issue currently.
I cannot ssh to the machines, although I suppose a Host only adapter to one of them would work.

Any ideas? Or am I going about this whole thing ass-ways?

[socratis]

I'll use a slightly paraphrased short description of the network modes, courtesy of scottgus1 (viewtopic.php?f=2&t=76188#p354679):

• NAT and NAT Service are like the network routers you use to separate your house network from the internet. NAT gives each guest its own "router" so to speak, so each guest is separated from the others and the host. NAT service allows more than one guest to attach to the "router" and be in their own private network together. Internet connection is possible.
• Bridged puts each guest on the host's physical network, and the guests looks to the physical network just like other new PCs on the network. You'll need a home/office router that acts as a DHCP server as well. Traffic between all guests and PCs and the internet is possible.
• Internal is a private network between the guests connected to it. You can have more than one internal network by giving new names to your new internal networks. You assign the guests to the internal network using the network's name. Internet connection is NOT possible.
• Host-only is an internal network that also includes the host. More than one guest can be attached to one host-only network. Internet connection is NOT possible.

For more details, see Chapter 6.2. Introduction to networking modes.

Plus, you can always have more than one network adapter to cover different case scenarios.

[Shougeki]

Thanks socratis. I was trying to keep it as simple as possible, but it looks like I will need a Host only which will cover all the VMs & Host, and then each host will require a NAT network for its internet access.

Nice one brother. Gonna give it a lash shortly.

B

[Shougeki]

Top of the pops mate. Blew away all the networking setup, created a new Host-only on the first adapter [so all the machines retained their static addresses]. Added a second NIC for NAT to each, and everything worked.

[socratis]

I always trusted and believed in you!