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

RE: [Xen-users] Ubuntu 8.04 Hardy Heron bridged networking xen connectivity loss



        It looks like you've spotted the problem (two NICs with the same
hwaddr and ipaddr), unfortunately, I'm not sure how you'd fix it
(scriptwise).  I always had problems with the scripts, so I disabled them
and just use the standard networking configuration files in Fedora 8.  This
works great, but most people tend to want Xen to deal with it.  Before that,
I tried several things, restarting xend was among them, it definitely made a
difference, but I don't remember whether it resolved or intensified the
problem.
        Regarding how you're getting rid of the bridge to make it work, I
think you should actually be getting rid  of the ipaddr on peth0, my bridge
and peth0 have the same hwaddr, and my bridge has the IP.  You may have to
use the route command to remove the extra routes afterwards too (or they may
go away on their own).  This will probably make it work, but would be
necessary again after reboots.
        Dustin

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Power
Sent: Wednesday, September 03, 2008 22:55
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Ubuntu 8.04 Hardy Heron bridged networking xen
connectivity loss

Last problem I had involved changing one character in my configuration 
scripts.  Really easy once someone showed me what was wrong.

Well I think this issue is just the same.  The moment I used apt to 
install the Xen kernal and tools I lost internet connectivity.  I have 
been managing because I can restore connectivity be deleting the bridge

mpower@dodtsair:~$ sudo ifdown eth0
mpower@dodtsair:~$ sudo brctl delbr eth0


But that means any domUs will not have connectivity.  I have not had any 
till now so it wasn't much of an issues.  But thanks to your help now I 
have XP running.

Ultimately I would really like you to show me the documentation that 
tells me how to fix this.  I am pretty sure it exists but my googling 
has not been effective in this area.

Some things that seem dubious to me are the fact that eth0(the bridge) 
looks like an exact clone of peth0 from ifconfig.  I would have expected 
them to have different HWaddr and at the very least different inet 
addr.  Another dubious thing is the routing table, double routes one for 
each interface.  Shouldn't that confuse the heck out of the OS?  Lastly 
I have no clue why the next line is in the routing table:
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0

Here is that status of my system on boot with networking broken:

mpower@dodtsair:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:22:15:3f:f2:0d 
          inet addr:75.101.5.130  Bcast:75.101.5.255  Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:fe3f:f20d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32133 (31.3 KB)  TX bytes:29676 (28.9 KB)

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:575 errors:0 dropped:0 overruns:0 frame:0
          TX packets:575 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:64462 (62.9 KB)  TX bytes:64462 (62.9 KB)

peth0     Link encap:Ethernet  HWaddr 00:22:15:3f:f2:0d 
          inet addr:75.101.5.130  Bcast:75.101.5.255  Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:fe3f:f20d/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:531 errors:0 dropped:80563353626 overruns:0 frame:0
          TX packets:497 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:45589 (44.5 KB)  TX bytes:54250 (52.9 KB)
          Interrupt:18 Base address:0xa000

mpower@dodtsair:~$ sudo brctl show
bridge name    bridge id        STP enabled    interfaces
eth0        8000.0022153ff20d    no        peth0

mpower@dodtsair:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
75.101.5.0      0.0.0.0         255.255.255.0   U     0      0        0 
peth0
75.101.5.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     1000   0        0 eth0
0.0.0.0         75.101.5.1      0.0.0.0         UG    0      0        0 
peth0
0.0.0.0         75.101.5.1      0.0.0.0         UG    100    0        0 eth0

mpower@dodtsair:~$ sudo ethtool eth0
Settings for eth0:
    Link detected: yes

mpower@dodtsair:~$ sudo ethtool peth0
Settings for peth0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000033 (51)
    Link detected: yes

mpower@dodtsair:~$ sudo /etc/Xen/scripts/network-bridge status
============================================================
10: peth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc 
pfifo_fast qlen 1000
    link/ether 00:22:15:3f:f2:0d brd ff:ff:ff:ff:ff:ff
    inet 75.101.5.130/24 brd 75.101.5.255 scope global peth0
    inet6 fe80::222:15ff:fe3f:f20d/64 scope link
       valid_lft forever preferred_lft forever
11: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
    link/ether 00:22:15:3f:f2:0d brd ff:ff:ff:ff:ff:ff
    inet 75.101.5.130/24 brd 75.101.5.255 scope global eth0
    inet6 fe80::222:15ff:fe3f:f20d/64 scope link
       valid_lft forever preferred_lft forever
 
bridge name    bridge id        STP enabled    interfaces
eth0        8000.0022153ff20d    no        peth0
 
75.101.5.0/24 dev peth0  proto kernel  scope link  src 75.101.5.130
75.101.5.0/24 dev eth0  proto kernel  scope link  src 75.101.5.130
169.254.0.0/16 dev eth0  scope link  metric 1000
default via 75.101.5.1 dev peth0
default via 75.101.5.1 dev eth0  metric 100
 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
75.101.5.0      0.0.0.0         255.255.255.0   U     0      0        0 
peth0
75.101.5.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     1000   0        0 eth0
0.0.0.0         75.101.5.1      0.0.0.0         UG    0      0        0 
peth0
0.0.0.0         75.101.5.1      0.0.0.0         UG    100    0        0 eth0
============================================================

I'll try the following before I send.

ifconfig eth0 mtu 1496

That didn't work.

Mike Power




_______________________________________________
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


 


Rackspace

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