1
1
I have a newbie networking question. In my office there are about 200 machines on 192.168.0.x IPs. At home I have a similar setup but with far fewer IPs. I run 5 virtual machines on my local machine and I have given them all 192.168.0.x IPs too but this seems wasteful because they only ever need to talk to one another. The default gateway is 192.168.0.1. Should I give my VMs IPs of 192.168.100.x ? 192.168.122.x ? What's so special about having VMs on 192.168.100.x / 192.168.122.x IPs ? If this is the right thing to do, what should the default gateway be set to ? I assume that if I have a VM with a 192.168.100.x address when it won't be able to use the 192.168.0.1 gateway ? Many thanks.
1There's nothing particularly special about the third octet of the address, whether it's 0, 1, 100, 122, or what-have-you; as long as the gateway and the machines are all on the same subnet, it'll work.
The default gateway can be whatever you like, but using 192.168.x.1 is typical -- if the VMs are on 192.168.100.x, then the gateway must be 192.168.100.something, and ideally will be 192.168.100.1.
Best way to do this would be with your VM host's NAT. Please identify your VM host (VirtualBox, VMware, &c., &c.) and I'll see if I can offer more specific advice on how to set that up. – Aaron Miller – 2012-10-02T12:37:29.657
@Aaron Miller Thank you. I'm using VirtualBox.. I'll experiment now after reading your tips +1. – ale – 2012-10-03T07:56:43.407