[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Alan Pearson <alandpearson@xxxxxxxxx>
  • Date: Thu, 22 Mar 2007 20:35:03 +0000
  • Delivery-date: Fri, 23 Mar 2007 09:04:22 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:Mime-Version:Content-Transfer-Encoding:Message-Id:Content-Type:To:From:Subject:Date:X-Mailer; b=GJtKP1IBInjCwzgSzYpyiODPZnvOWCAcahaLM1j+dfAWA7RjDeyk2WaJkEp8KeJemjsk0Dbeo9B5JerWzXlYVu4JrPOHVsLNy9Yp3xShAkHbokOfsOR0Iv+GwGF7CGowrpvGHtBX5D/rHc/IC0HzLb391AvqB3OxBu4exqQtVZ4= ;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Folks,

I've been using Xen 3.0.2-2 for quite a while now on various RHEL 4.3 (host + guests, using xensource RPMs) systems, successfully.

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.


Any help at all, gratefully received, and if I have not provided enough information, please ask.



Some Info :

vif5.0 is the interface associated with my DomU.
The 172.16.5.X subnet is the one giving the trouble (eth1 is just used for accessing the box for the moment until I can get it working, so the 10.2.2.X addresses can be ignored.)





[root@xen-srv2 /]# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0
                                                        vif5.0




[root@xen-srv2 /]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:5E:DE:BB:DA
inet addr:172.16.5.33 Bcast:172.16.5.63 Mask: 255.255.255.224
          inet6 addr: fe80::214:5eff:fede:bbda/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2016 (1.9 KiB)  TX bytes:5172 (5.0 KiB)

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:92809 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122427 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6684042 (6.3 MiB)  TX bytes:20822432 (19.8 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:449 errors:0 dropped:0 overruns:0 frame:0
          TX packets:449 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:42171 (41.1 KiB)  TX bytes:42171 (41.1 KiB)

peth0     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:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2464 (2.4 KiB)  TX bytes:20184 (19.7 KiB)
          Interrupt:19 Memory:c8000000-c8011100

vif0.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:106 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5172 (5.0 KiB)  TX bytes:2016 (1.9 KiB)

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:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:107 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:1784 (1.7 KiB)  TX bytes:5496 (5.3 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:110 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:3674 (3.5 KiB)  TX bytes:0 (0.0 b)





---
AlanP



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.