Hi Vincent,
I was wrong saying that NAT attachment has an internal network
implicitly created for it. Internal networks are created for all
attachment types except NAT. Anyway I created the setup you'd
described and could not reproduce the problem with the current version
of VirtualBox. What are IP addresses of client/bridge/gateway, btw?
Regards,
Aleksey
On Jun 15, 2009, at 12:30 PM, Aleksey Ilyushin wrote:
Hi Vincente,
The problem is in your client.xml. You use NAT attachment instead of
internal network. This causes both the gateway and the client to be
attached to the same internal network implicitly created for NAT
attachment.
Regards,
Aleksey
On Jun 12, 2009, at 4:13 PM, Vicente Aguilar wrote:
Hi
I'm trying to setup a three-VM network, one of them acting as a
bridge between the other two. The two connections to this bridge VM
are internal networks, with different names. The setup looks like
this:
clientVM -- LAN --> bridgeVM -- WAN --> gatewayVM --> NAT
The problem is that even the two internal networks are named
differently (LAN and WAN), they actually work like one single
network: there's no traffic separation between them, all the
traffic reaches both networks. In other words: even if the bridge
isn't running, there is visibility between the client VM and the
gateway one, i can ping the gateway VM from the client and viceversa.
I've taken a look at the config xml files, just in case the network
names weren't there. They are, everything seems OK to me:
bridge.xml: <InternalNetwork name="LAN"/>
bridge.xml: <InternalNetwork name="WAN"/>
client.xml: <InternalNetwork name="LAN"/>
gateway.xml: <InternalNetwork name="WAN"/>
Please find the full config files attached.
Am I doing something wrong? Is this a limitation of VBox?
Host: ubuntu 9.04 64bits
VirtualBox 2.2.4 (from www.virtualbox.org, not OSE)
Guests: client WindowsXP, gateway and bridge RedHat EL4.
Thanks in advance.
Regards,
--
Vicente Aguilar <[email protected]> | http://www.bisente.com
<configfiles.tar.bz2>_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
