Package: xen-utils-common Version: 3.2.0-2 Severity: normal Hi,
we have a setup with a system that has multiple ethernet interfaces. There is a interface eth2 which has an IP configured and is connected to the network and which is used to administrate that. Another iface is supposed to be used as netdev (eth0). This interface is unconfigured but connected to a network to which the DomUs are supposed to be connected. This setup does not work with the network-bridge script, because it does not bring eth0 up, after it became the bridge and in consequence the DomUs do have link, but no network connectivity. I guess the problem lies in the do_ifup function which tries to call ifup to bring the new interface (bridge with the name of the original eth device) up. There is an alternative code path which I guess is supposed to be called if devices are not in /e/n/interfaces, where the script expects that ifup would exit with a non-zero exit code. However if a device is not configured in /e/n/interfaces an "ifup interface" returns still a exit 0, therefore this code path is never used. So eventually the script should not rely on ifup failing with a non-zero exit code if the interface is not configured in /e/n/interfaces but instead look if the interface is up after that. Best Regards, Patrick -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
