Javier Guerra wrote:
On Fri, Sep 19, 2008 at 5:42 PM, David Dyer-Bennet <dd-b@xxxxxxxx> wrote:
I know I'm confused about *something*, because packets aren't getting
through.
The hardware has two NICs, eth0 connects to the corporate lan on
192.168.1.14, and to a private cluster lan on 172.17.0.1.
In dom0, I can reach systems on both lans.
In a guest on 172.17.1.2, I can't reach anything. Nothing in 172.17,
nothing in 192.168.1. The guest is domain 9, called vl01.
In dom0 A bridge, xenbr0 (specified in my control files for the domains),
is set up to let everybody talk to everywhere.
[root@prcapp02 xen]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.2ed4b2e93fd1 no vif9.0
vif7.0
tap0
peth0
vif0.0
where's the 'way out' from xenbr0? IOW, is peth0 connected to a real NIC?
Yes, that's the "real" nic. Xen seems to have renamed the interfaces.
i think you should set two bridges, one connected to eth0
(192.168.1.14) , and the other to eth1 (172.17.0.1), then if you want
a DomU on 172.17.x.x, connect it's vif to the second bridge.
A bridge is a MAC-layer device, it never even looks at the IP address in
the packet (the packet need not, in fact, be IP at all). So I'd need a
pretty detailed explanation of how this might help before it's even
worth trying.
--
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home