Xen project Mailing List

Re: [Xen-users] DOM0 networking - dead to the outside world

From: "Alan Pearson" <alandpearson@xxxxxxxxx>

Date: Fri, 23 Mar 2007 18:01:21 -0000 (GMT)

Delivery-date: Fri, 23 Mar 2007 11:00:39 -0700

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:Received:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=j/WiQM7gg+g8Du7UJoPLyUO109saZqSHQEt1E39T7U9DgavHp+uDFyaOC14w9wnVr+PXuHFZ1U7bt3GmOZ6z4iafFte6HtirKQ0E0fXqk0PAtTlG4BucYDU0kgGMjORnIxf4e41H/5tLoEIyWr4M9WnJadL/u+nE/muOF+xx824= ;

Importance: Normal

List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Jez Something wierd going on, I don't get the bridge device brought up (I presume this should be done with service network start). So after service network start I get this : [root@xen-srv2 network-scripts]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:14:5E:DE:BB:DA UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:34 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2366 (2.3 KiB) TX bytes:14320 (13.9 KiB) Interrupt:19 Memory:c8000000-c8011100 eth1 Link encap:Ethernet HWaddr 00:14:5E:DE:BB:DC inet addr:10.2.2.1 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::214:5eff:fede:bbdc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:96692 errors:0 dropped:0 overruns:0 frame:0 TX packets:124994 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7027654 (6.7 MiB) TX bytes:21223048 (20.2 MiB) Interrupt:16 Memory:ce000000-ce011100 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1652 errors:0 dropped:0 overruns:0 frame:0 TX packets:1652 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:151876 (148.3 KiB) TX bytes:151876 (148.3 KiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST NOARP MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:450 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3908 (3.8 KiB) TX bytes:19116 (18.6 KiB) veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:74 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6468 (6.3 KiB) TX bytes:0 (0.0 b) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST NOARP MTU:1500 Metric:1 RX packets:450 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19116 (18.6 KiB) TX bytes:3908 (3.8 KiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:74 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:6468 (6.3 KiB) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:30 errors:0 dropped:0 overruns:0 frame:0 TX packets:3387 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:2008 (1.9 KiB) TX bytes:148960 (145.4 KiB) No ip address on eth0 and no xbr0 device. ? [root@xen-srv2 network-scripts]# brctl show bridge name bridge id STP enabled interfaces [root@xen-srv2 network-scripts]# So am I doing something wrong ? I'd expect to see a bridge device with an IP address ? -- AlanP On Fri, March 23, 2007 5:32 pm, jez wrote: > 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. >> > > Hi Alan > > can't tell you what the problem is, but a similar problem popped up last > week and the proposed solution was to create your own bridge. The start > of the thread (subject: dom0 networking disabled) is here: > > http://lists.xensource.com/archives/html/xen-users/2007-03/msg00636.html > > A possible RedHat configuration is here: > > http://lists.xensource.com/archives/html/xen-users/2007-03/msg00697.html > > HTH > > jez > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.