This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Problems with bridged networking

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Problems with bridged networking
From: "Angel L. Mateo" <amateo@xxxxx>
Date: Wed, 17 Sep 2008 08:05:54 +0200
Delivery-date: Tue, 16 Sep 2008 23:06:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48CE7874.2090102@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: ATICA, Universidad de Murcia
References: <48C6888A.3090500@xxxxxxxxx> <48CE7874.2090102@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
El lun, 15-09-2008 a las 17:00 +0200, Thomas Robers escribió:
> Hi,
> I've now tested Xen 3.2 from backports.org on a Debian 4.0 test
> machine with 7 Interfaces and the problem is in the script
> 'network-bridge'.
> There's a function 'do_ifup' in it which I have modified and after
> modification Xen 3.2 works on my Debian machine. I found that
> with Xen 3.2 the bridges were there but not up and everything
> works as expected when I did a 'ifconfig xenbrX up'.
> Before modification:
>       do_ifup() {
>       if ! ifup $1 ; then
>           if [ -n "$addr_pfx" ] ; then
>               # use the info from get_ip_info()
>               ip addr flush $1
>               ip addr add ${addr_pfx} dev $1
>               ip link set dev $1 up
>               [ -n "$gateway" ] && ip route add default via ${gateway}
>           fi
>          fi
> }
> After modification:
>       do_ifup() {
>          ifconfig $1 up
>          if [ -n "$addr_pfx" ] ; then
>              # use the info from get_ip_info()
>              ip addr flush $1
>              ip addr add ${addr_pfx} dev $1
>              ip link set dev $1 up
>              [ -n "$gateway" ] && ip route add default via ${gateway}
>          fi
> }
> So that way it works for me for now. But could there be any other
> drawback except for further updates? I also haven't really found out
> what this test with 'ifup' is really for. Can anybody explain what's
> happening there? I saw this message from 'ifup' when it got executed
> (e.g. for xenbr6):
        I haven't check the rest of the scripts, but ifup is a debian command
to bring an interface up (and returns zero is everything is ok). So your
code and the original are different ways to do the same (I haven't tried
to find out why yours works and the other doesn't).

Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información       _o)
y las Comunicaciones Aplicadas (ATICA)      / \\
http://www.um.es/atica                    _(___V
Tfo: 968367590
Fax: 968398337

Xen-users mailing list