Weirdest thing I haven’t seen before.
When I launch 2 VBox guests at the same time, I found that they both are assigned the same IPv4 address.
Oracle VBox 4.3 install (from Oracle, not from OSS repos)
Guests are both configured with NAT (address assigned using DHCP)
Guests are configured and verified with different MAC addresses.
Additional:
Determined in the network settings that the IPv6 address is also different (besides the MAC address).
All other network settings are identical.
Affected:
All VBox guests no matter the OS, have verified openSUSE 13.1, CentOS 6.4, WindowsXP so far.
Does not seem to affect network functionality. Each Guest can access external networks (like the Internet) through NAT simultaneously.
The only issue seems to be that they cannot communicate with each other using an IPv4 address (of course, since they have the same IPv4 address).
Wondering if anyone else running VBox is seeing the same thing?
> Wondering if anyone else running VBox is seeing the same thing?
I don’t, but I’m only running version 4.2. But I use NAT and do run
multiple VMs (actually cloned VMs from the same base, too) and this isn’t
a problem for me.
On 11/29/2013 03:44 PM, Jim Henderson wrote:
> On Thu, 28 Nov 2013 20:16:03 +0000, tsu2 wrote:
>
>> Wondering if anyone else running VBox is seeing the same thing?
>
> I don’t, but I’m only running version 4.2. But I use NAT and do run
> multiple VMs (actually cloned VMs from the same base, too) and this isn’t
> a problem for me
I am running 4.3.4, which I just installed today, and I am seeing the same
situation. A Windows XP and an openSUSE 12.3 VM both have 10.0.2.15 as their IP.
> I am running 4.3.4, which I just installed today, and I am seeing the
> same situation. A Windows XP and an openSUSE 12.3 VM both have 10.0.2.15
> as their IP.
You could use manual network setup instead of dhcp, in the clients. Not
optimal, but would solve the issue.
You should also check that they different MAC addresses.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Resolved.
Apparently this is an anomaly unique(hopefully) to the default NAT Network.
I now understand what the “NAT network” configuration option is (yes, it’s different than the NAT option).
With the “NAT network” option you can define new NAT networks and so I configured a new network with DHCP enabled.
So far, it seems to be working as expected… When multiple Guests are launched, each acquire their own IP address.
NAT: experimental virtual router mode: several VMs are attached to the same internal network and share one NAT service (see the manual for more information)
Yes, I read that and might have interpreted differently than you…
“the same internal network” does not necessarily mean that all use the same IP address. A “network” comprises any number of networks, and once the Guest is running, you’ll see the subnet mask used allows for many addresses.
So no, in the statement you quoted I saw nothing that describes what I discovered.
