https://bugzilla.novell.com/show_bug.cgi?id=419095 User llipavsky@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c9 --- Comment #9 from Lukas Lipavsky <llipavsky@novell.com> 2008-09-22 07:56:29 MDT --- There are several yast issues here, marked as *bugN* in the text: Problem 1: described in comment 3 When new bonding device is created/edited, it allows only unconfigured devices to be added to the bond. Other devices - especially those configured to be bonding slaves - aren't shown on the list (*bug1*). This list should definitely include devices that are configured as bonding slaves (no IP address) as well! And when device is set to be bonding slave for some bond, it should be configured as bonding slave and not remain unconfigured(*bug2*). Another bug - as described in comment 3 - is that no device are shown in bonding-slaves list when any device has configuration set to 'no IP address'(*bug3*). Problem 2: described in comment 6 The device that is bridged should have ip 0.0.0.0/24 (as described in http://en.opensuse.org/YaST/Network/11.0-bridge). (BTW This is first problem since it should be 'no IP address' configuration instead of 0.0.0.0/24 which is weird. *bug4*) If it has different configuration, yast will inform you that it's configuration will be *removed*. And removes it. Together with bonding device since it's pure virtual - *bug5*. When the yast finish, the bond configuration is gone, thus the bridge has nothing to connect with, and is unusable. If the bond0 is set up with ip 0.0.0.0/24 bridge can be successfully created... -- 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.