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

[Xen-users] lost network connectivity after update to 3.0.3



Centos 5.1, an updated kernel and xen were pushed out RH, i believe in response to a rash of security bugs found. i updated my guest instances, rebooted them, they were still reachable. updated domU and rebooted, and now the guests are no longer reachable. figuring i fubarred the proper steps i destroyed then created the instances again - still no go.

domU is running:
kernel-xen-2.6.18-53.1.21.el5
xen-3.0.3-41.el5_1.6
xen-libs-3.0.3-41.el5_1.6

and the guests are running:
kernel-xen-2.6.18-53.1.21.el5

right now i have only one guest up (why bother with the others running. on domU, if have the following IFs:

eth0 Link encap:Ethernet HWaddr 00:30:48:C0:6C:5A inet addr:10.255.40.100 Bcast:10.255.40.255 Mask:255.255.255.0
         inet6 addr: fe80::230:48ff:fec0:6c5a/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:39458 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1113 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:2433216 (2.3 MiB)  TX bytes:133979 (130.8 KiB)
         Interrupt:19 Base address:0xa000

eth0:1 Link encap:Ethernet HWaddr 00:30:48:C0:6C:5A inet addr:10.255.40.101 Bcast:10.255.40.255 Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         Interrupt:19 Base address:0xa000

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:130 errors:0 dropped:0 overruns:0 frame:0
         TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:16056 (15.6 KiB)  TX bytes:16056 (15.6 KiB)

vif6.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:451 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:32
         RX bytes:18682 (18.2 KiB)  TX bytes:0 (0.0 b)

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:4125 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:121554 (118.7 KiB)  TX bytes:0 (0.0 b)

and the routing table on domU is:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 10.255.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.255.40.1 0.0.0.0 UG 0 0 0 eth0

which is correct. brctl show returns the following:

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif6.0

on the guest i have:
eth0 Link encap:Ethernet HWaddr 00:16:3E:2C:CF:7E inet addr:10.255.40.110 Bcast:10.255.40.255 Mask:255.255.255.0
         inet6 addr: fe80::216:3eff:fe2c:cf7e/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:479 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 b)  TX bytes:26172 (25.5 KiB)

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:365 errors:0 dropped:0 overruns:0 frame:0
         TX packets:365 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:32683 (31.9 KiB)  TX bytes:32683 (31.9 KiB)
and the routing table is
Destination Gateway Genmask Flags MSS Window irtt Iface 10.255.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.255.40.1 0.0.0.0 UG 0 0 0 eth0

which again is exactly as expected. interestingly, after xm console'ing to a guest instance, i can ping, traceroute, and even ssh to *another* guest instance - but not to the domU or to any other network besides the other guests.

i'm baffled. i'm unclear what exactly broke, or why/how it broke - and most importantly, how to fix it. i've been googling for hours.

thoughts, suggestions, brickbats, ?

--
Paul Theodoropoulos

Attachment: PGP.sig
Description: PGP signature

_______________________________________________
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®.