https://bugzilla.novell.com/show_bug.cgi?id=407878 User kssingvo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=407878#c1 --- Comment #1 from Klaus Singvogel 2008-07-24 03:58:59 MDT --- Any news? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=407878 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=407878#c2 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kssingvo@novell.com --- Comment #2 from Tambet Ingo 2008-08-02 06:25:01 MDT --- Basically, the yast configuration doesn't match NetworkManager behavior very well: In yast, you can define one connection for a device and set it's activation to "manual", so NM will not automatically activate it. However, NM supports multiple different configurations for a device and if one of these matches the essid and is configured to automatically connect, NM would use that and connect automatically. Have a look in the NM's connection editor and make sure you don't have any defined wireless connections where "Connect automatically" is checked. You forgot to attach your /etc/sysconfig/network/ifcfg-wlan0 file. I'm asking it because if in yast, you only set the device as "activate manually" and do not fill the network essid, then NM ignores the connection (a wireless connection is invalid without essid). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=407878 User kssingvo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=407878#c4 --- Comment #4 from Klaus Singvogel 2008-08-05 03:23:21 MDT --- Created an attachment (id=231725) --> (https://bugzilla.novell.com/attachment.cgi?id=231725) ifcfg-wlan0 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=407878 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=407878#c6 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Tambet Ingo 2008-11-17 02:54:28 MST --- Because of this bug (and many similar ones), opensuse 11.1 makes a clear distinction between "traditional" method and NetworkManager. NM uses only it's own configuration (accessible from control center and applet's right-click menu). So there shouldn't be any confusion anymore wrt yast configuration, it's possible to set NM connection properties to not be activated manually, so I'm closing this bug. The wireless hardware state monitoring (rfkill) is a big issue in Linux (there's no unified API) so NM supports only some cards. There are multiple bug open for it: 398473, 443568, 444364. Please add yourself to the CC list in these. -- 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.