[ale] virtualbox nat

[Brian Mathis]

The regular NAT mode of VirtualBox creates a separate virtual network for
EACH VM, so all four of your VMs are essentially behind their own separate
NAT device, creating 4 separate networks.  I agree this is braindead but it
is historically been how they handled it, and it still seems to be the
default.

You probably want to use the "NAT Network" mode, which acts more like a
single home router with all VMs on the same network behind it.  Or you
might want Bridged mode, which puts the VMs directly on your home network
and bypasses internal NAT altogether.  The list of modes is outlined here:
https://www.virtualbox.org/manual/ch06.html#networkingmodes


❧ Brian Mathis
@orev


On Tue, Dec 30, 2014 at 11:34 PM, Narahari 'n' Savitha <savithari at gmail.com>
wrote:

> Folks:
>
> If I have say 4 VM's under Virtualbox, I was expecting each of them to
> receive 4 sep ip's like
> 10.0.2.15
> 10.0.2.16
> 10.0.2.17
> 10.0.2.18
>
> But I always see only 10.0.2.15 for all of them (driving me nuts as to how
> they can NAT it this way, my router will not allow this and it dishes out
> distinct ip's to each machine) so Virtualbox is crazy.
>
> The above situation of same ip for all VM's is causing me to open unique
> ports for SSH access to each of the VM's causing me to remember ports
> rather than ip's (prefer to rem names)
>
> How to make VirtualBox behave like a normal router for NATing ?
>
> What is the eq of kvm on Mac's ?
>
> Regards,
> -N
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20141231/e7580313/attachment.html>