Re: [Xen-users] Problems with bridged networking

[Thomas Robers <robers@xxxxxxxxx>]

Mike Power schrieb:
> At some point I am guessing around 3.1 the bridge network scripts 
> changed the resulting bridge configuration they produced.
> You can see some diagrams here:
> http://wiki.xensource.com/xenwiki/XenNetworking#head-708d4c55f42b5e2b866c06e1ae69530e8c748799 
>
>  From my quick reading of your problem your domU config files probably 
> still point at the nonexistent bridge xenbr0.  Take a look at the link I 
> sent you to help you understand what your scripts are doing and that 
> should get you on the road to setting up your networking the way you 
> want.  At very least the link should show you that the new bridge name 
> will be something like eth0.
Hi Mike,

thank you for your answer. I looked at wiki entry and as Steffen also told
me, I can see, that in Xen 3.2.x the bridge names have changed from 3.1.x -> 
3.2.x
So I tried what I found in almost every howto and book:

        server:/etc/xen/scripts# ./network-bridge bridge=eth1 netdev=eth1 start
        ifdown: interface eth1 not configured
        Nothing to flush.
        Waiting for peth1 to negotiate link......
        Ignoring unknown interface eth1=eth1

for the eth1 interface and a brctl afterwards:

        server:/etc/xen/scripts# brctl show
        bridge name     bridge id               STP enabled     interfaces
        eth0            8000.000e0c43ab3d       no              peth0
        eth1            8000.000e0c43ab3e       no              peth1

shows that there is an bridge named eth1 but the domU which formerly used
'xenbr1' doesn't start with the bridge named eth1. I tried this in the
config file for domU

        vif = [ 'bridge=eth1' ]

The domU starts but there is no network connection possible. I thought that
the 'network-bridge' script would set up the bridge and put it up a ifconfig
doesn't show an interface eth1 only peth1.

Now I've booted Xen 3.0.3 again and almost everything works as expected. After
booting all bridges are up and working

        xenbr1    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:43:AB:3E
                  inet6 Adresse: fe80::20e:cff:fe43:ab3e/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:186 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:26111 (25.4 KiB)  TX bytes:468 (468.0 b)

        xenbr2    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F4
                  inet6 Adresse: fe80::20e:cff:fec5:1af4/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:163 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:22984 (22.4 KiB)  TX bytes:468 (468.0 b)

        xenbr3    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F5
                  inet6 Adresse: fe80::20e:cff:fec5:1af5/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:134 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:18998 (18.5 KiB)  TX bytes:468 (468.0 b)

        xenbr4    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F6
                  inet6 Adresse: fe80::20e:cff:fec5:1af6/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:208 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:32637 (31.8 KiB)  TX bytes:468 (468.0 b)

        xenbr5    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F7
                  inet6 Adresse: fe80::20e:cff:fec5:1af7/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:273 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:37964 (37.0 KiB)  TX bytes:468 (468.0 b)

        xenbr6    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:14:95
                  inet6 Adresse: fe80::20e:cff:fec5:1495/64 
Gültigkeitsbereich:Verbindung
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:3396 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
                  Kollisionen:0 Sendewarteschlangenlänge:0
                  RX bytes:497298 (485.6 KiB)  TX bytes:468 (468.0 b)

I did this with the wrapper script:

        /etc/xen/scripts/network-bridge start vifnum=0 bridge=xenbr0 netdev=eth0
        /etc/xen/scripts/network-bridge start vifnum=1 bridge=xenbr1 netdev=eth1
        /etc/xen/scripts/network-bridge start vifnum=2 bridge=xenbr2 netdev=eth2
        /etc/xen/scripts/network-bridge start vifnum=3 bridge=xenbr3 netdev=eth3
        /etc/xen/scripts/network-bridge start vifnum=4 bridge=xenbr4 netdev=eth4
        /etc/xen/scripts/network-bridge start vifnum=5 bridge=xenbr5 netdev=eth5
        /etc/xen/scripts/network-bridge start vifnum=6 bridge=xenbr6 netdev=eth6


Do you have any further suggestions where I could look?

Many Thanks.
Thomas


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