thr3ads.net - Pkg xen devel - [Pkg-xen-devel] network-bridge called three times [May 2008]

If this information is useful, please help other people find it:
Share via:

Alex Volkov

2008-May-04 01:44 UTC

[Pkg-xen-devel] network-bridge called three times

Hello All,
I'm trying to figure out why xen-utils-common 3.2 doesn't suport
bridging on multiple interfaces. I've been digging
around /etc/xen/scripts/network-bridges. And modified it so that during
boot, when executed the script writes into /tmp/netbr file, but I
commented out code that actually creates bridges.

I discovered that this script is called three times during boot, I
checked all files under /etc/xen and the only place that mentions
(network-script network-bridge) is  in /etc/xen/xend-config.sxp, and it
is mentioned there once.

Is this normal behaviour or is something wrong?

I attached both my modified script and output logfile, note that my
computer has two network interfaces - eth0 and eth1

Alex.
-------------- next part --------------
Sat May  3 21:34:34 EDT 2008
Network bridge values: 'start' 
*****IP link parameters before script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
*****IP link parameters after script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
Device list= -eth1
eth0-
netdev ^eth1^
netdev ^eth0^
Sat May  3 21:34:34 EDT 2008
Network bridge values: 'start' 
*****IP link parameters before script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
5: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
6: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
*****IP link parameters after script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
5: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
6: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
Device list= -eth1
eth0-
netdev ^eth1^
netdev ^eth0^
Sat May  3 21:34:37 EDT 2008
Network bridge values: 'start' 
*****IP link parameters before script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
5: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
6: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
*****IP link parameters after script import
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:cf:de brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.22/24 brd 172.16.200.255 scope global eth0
    inet6 fe80::280:2dff:fe8f:cfde/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:80:2d:8f:d2:d3 brd ff:ff:ff:ff:ff:ff
    inet 172.16.200.23/24 brd 172.16.200.255 scope global eth1
    inet6 fe80::280:2dff:fe8f:d2d3/64 scope link 
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
5: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
6: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
Device list= -eth1
eth0-
netdev ^eth1^
netdev ^eth0^
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network-bridge
Type: application/x-shellscript
Size: 7986 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080503/02d6401b/attachment.bin

Bastian Blank

2008-May-04 07:41 UTC

head link

[Pkg-xen-devel] network-bridge called three times

On Sat, May 03, 2008 at 09:44:13PM -0400, Alex Volkov
wrote:> I'm trying to figure out why xen-utils-common 3.2 doesn't suport
> bridging on multiple interfaces. I've been digging
> around /etc/xen/scripts/network-bridges. And modified it so that during
> boot, when executed the script writes into /tmp/netbr file, but I
> commented out code that actually creates bridges.
Don't use network-bridge. It just breaks most the time.

It seems that it is time to add a ifupdown script which does this work,
any volunteer?

Bastian

-- 
The heart is not a logical organ.
		-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4

Alex Volkov

2008-May-04 18:09 UTC

head link

[Pkg-xen-devel] network-bridge called three times

> Don't use network-bridge. It just breaks most the time.
>
> It seems that it is time to add a ifupdown script which does this work,
> any volunteer?
>
> Bastian
Does this mean adding /etc/xen/scripts/network-bridge using post-up
command? network-bridge as I noticed doesn't have all that many bugs
and it is definitely fixable, I'm just wondering what is wrong with the
code that calls it when I declare it from xend-config.sxp? 
> Well, does what work? ifupdown has everything needed to create bridges, so
I
> don't think anything is missing... And we have documentation in the
package
> about how to configure it... :) Putting something like network-bridge (ie.
an
> hack modifying the current configuration guessing what the user wants
rather
> than what the configuration is) I think is not going to fly... :)
>
> Thanks!!
>
> Guido
Could you point me to the documentation, I mostly googled around to
find a fix for it, but didn't find anything useful.

Alex.

Possibly Parallel Threads

Search for more apparently analagous threads

Pkg xen devel - May 2008 - network-bridge called three times

[Pkg-xen-devel] network-bridge called three times

[Pkg-xen-devel] network-bridge called three times

[Pkg-xen-devel] network-bridge called three times

Possibly Parallel Threads