[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] DOM0 networking - dead to the outside world
It's probably iptables: I've not seen a good write-up on how to deal with this, but if you don't need or want iptables filtering Dom0, you can disable it.On Thu, Mar 22, 2007 at 08:35:03PM +0000, Alan Pearson wrote:Now I have the pleasure installing Xen 3.0.4.1 on RHEL4.4 (host + guests, using xensource RPMs) system, and I'm having a nightmare with Dom0 networking.The DomUs can see the outside world AND the Dom0 eth0 address, but Dom0 cannot see the outside world nor the outside world see it.Dom0 can ping the guests fine, and the guests can ping Dom0.For the purposes of this discussion, outside world means 'same subnet on the physical interface'Dom0 networking works fine before network-bridge is started, after it starts, no more Dom0 networking.I've really no idea what is wrong, and hours and hours playing with Linux bridging has got me nowhere ;-( There doesn't seem to be any iptables rules stopping traffic, and selinux is disabled.The output of the brctl show & ifconfig commands looks identical on the xen3.0.4.1 to the working 3.0.2-2 systems, so I'm lost.Running tcpdump -s0 -L -A produces no output on any interface. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |