http://bugzilla.novell.com/show_bug.cgi?id=547327
User casualprogrammer@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=547327#c2
--- Comment #2 from Casual J. Programmer 2009-10-27 04:33:32 MDT ---
The problem is not YaST not accepting the 0.0.0.0/32 configuration, rather it
lets the user in the dark about this necessity.
What it currently does, if a bridge is configured and the participating NICs
are confifured otherwise, it simply brings up a message box, stating that "At
least one selected device is already configured. Remove the configuration ?
Cancel/Continue". Continue resets (deletes) the existing configuration
(including the authorization part of the WLAN), cancel returns to the bridge
interface selection.
Instead of resetting the configuration, it could just go ahead and configure
the selected NICs to 0.0.0.0/32 and check that bridge and selected NICs have
identical MTU settings.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
