Patrick Schoenfeld
2009-Jan-12 13:39 UTC
[Pkg-xen-devel] Bug#511579: network-bridge script does not work if netdev is not in /e/n/interfaces
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
Debian Bug Tracking System
2012-May-06 13:54 UTC
[Pkg-xen-devel] Bug#511579: marked as done (network-bridge script does not work if netdev is not in /e/n/interfaces)
Your message dated Sun, 6 May 2012 15:51:34 +0200 with message-id <20120506135134.GA12056 at wavehammer.waldi.eu.org> and subject line network-bridge not supported has caused the Debian Bug report #511579, regarding network-bridge script does not work if netdev is not in /e/n/interfaces to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 511579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511579 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Patrick Schoenfeld <schoenfeld at debian.org> Subject: network-bridge script does not work if netdev is not in /e/n/interfaces Date: Mon, 12 Jan 2009 14:39:44 +0100 Size: 3826 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/0f07bb27/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: network-bridge not supported Date: Sun, 6 May 2012 15:51:34 +0200 Size: 1515 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120506/0f07bb27/attachment-0001.mht>
Maybe Matching Threads
- xen-4 dom0 bridge failed to bring up eth1
- Bug#655581: xen-utils-common: network-bridge breaks the network setup when using ethernet bonding.
- Bug#543479: network-bridge doesn't handle secondary address of ${netdev}
- scaled Schoenfeld residuals
- Bug#588477: [PATCH] hotplug: network-bridge: fix for interfaces with no gateway