virtualbox.org

I have configured Guest 1 (a net boot loader appliance) with Adapter 1 as "internal network", Guest 2 with Adapter 1 as "internal network" as in Guest 1, and Adapter 2 as NAT. Guest 1 works as a dhcp client, pointing to Guest 2 Adapter 1 (eth0 configured as static IP 192.168.201.1, net mask 255.255.255.0). Guest 2 Adapter 2 (eth1 configured as dhcp client).

This is the good news: Guest 1 Adapter 1 and Guest 2 Adapter 1 are communicating as desired. Guest 2 Adapter 2, can access the Internet through the host wireless connection.

These are the bad news: Host can not ping the Guest 2 when pointing to eth1's IP. Of course, eth0 IP wouldn't be reachable. The other weird thing is that the dhcp client eth1 interface get's assigned to IP 10.0.3.15 consistently, without any visible dhcp other than the one installed on Guest 2 (range 192.168.201.100 - 200) and the home area network which hosts receive DHCP IPs in the range 192.168.1.1 - 192.168.1.x (I think x = 50).

Another data: If I set Adapter 2 (eth1) as static with 192.168.201.2 there remains no interconnection between Guest 2 and host.

By the way: Guest 2 is a Debian Linux, and Host is a MacBookPro.

Any experience with this scenario or similar? If not, any clue will be mostly appreciated. If you think I need to add a static route, how do I proceed on the BookMacPro?

Thanks you

Luiz

That is to be expected. If the guest is on an internal network linked to the physical network by a NAT connection, the host (or any other physical machine) will not be able to access the guest behind the NAT. NAT is a one-way translation; you can access the "public" side from the "private" sde but not vice versa.

If you really want to access the guest from the host, give the guest an additional NIC and use Host Only for it.