https://bugzilla.novell.com/show_bug.cgi?id=847783 https://bugzilla.novell.com/show_bug.cgi?id=847783#c0 Summary: Bridge does not add ethX interfaces when they're marked "on cable connection" and offline during system start Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: HP OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: spoil@spoilbase.zapto.org QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 1. Go to YAST2 - Network Devices. 2. Configure a couple of eth-interfaces (in my case: eth1, eth2, eth3, eth4 on an Intel igb board, eth5 on a Realtek-add-on-card, eth6 as an on-board-Broadcom) 3. Mark them as active "on cable connection" in YAST2 4. Add a bridge (in my case br0) 5. Mark that bridge as brought up "on boot". 6. Add the nethwork interfaces (see no. 2) as bridged devices. 7. Save. 8. Configure the dhcpd to serve br0, Save, reboot. Expected behaviour: The bridge should be permanent, while the eth-interfaces may be switched off for power saving. The eth-devices should become active as they detect a cable connection and start communicating with br0. Found behaviour: Those eth-devices that were plugged in during boot do work as expected. All others are not added to the bridge. When the formerly inactive eth-devices receive a cable, they do come up as expected, but they do not get added to the bridge and thus do not receive dhcp addresses. The remain connected but dead. Analysis: "brctl show" shows that only those devices that were plugged in during boot up get added to the bridge. Those that were offline during boot, never appear on the bridge, regardless of whether they're connected to a cable or not. Workaround: Add interfaces manually ("brctl addif ethX") somewhen after boot. I actually added a cron-job that waits for a minute after reboot and then adds all the required interfaces. Finding: The config scripts seem to handle this scenario very misleadingly. Reproducible: Always Steps to Reproduce: 1. Go to YAST2 - Network Devices. 2. Configure a couple of eth-interfaces (in my case: eth1, eth2, eth3, eth4 on an Intel igb board, eth5 on a Realtek-add-on-card, eth6 as an on-board-Broadcom) 3. Mark them as active "on cable connection" in YAST2 4. Add a bridge (in my case br0) 5. Mark that bridge as brought up "on boot". 6. Add the nethwork interfaces (see no. 2) as bridged devices. 7. Save. 8. Configure the dhcpd to serve br0, Save, reboot. Actual Results: Those eth-devices that were plugged in during boot do work as expected. All others are not added to the bridge. When the formerly inactive eth-devices receive a cable, they do come up as expected, but they do not get added to the bridge and thus do not receive dhcp addresses. The remain connected but dead. Expected Results: The bridge should be permanent, while the eth-interfaces may be switched off for power saving. The eth-devices should become active as they detect a cable connection and start communicating with br0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.