[Bug 222131] New: Knetwork Manager Activation Stalls At 28%
https://bugzilla.novell.com/show_bug.cgi?id=222131 Summary: Knetwork Manager Activation Stalls At 28% Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: stbedi@yahoo.com QAContact: qa@suse.de Knetwork Manager stalls at 28% when I use it to access a wireless network connection. I have installed NDIS Wrapper and followed the instructions supplied by SUSE linux under /usr/share/doc/packages/ndiswrapper (as I did when using SUSE 9.3). The connection stalls out at 28% when I use Knetwork Manager. Any suggestions on this? Thanks, STB -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jg@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 jg@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@ximian.com, thoenig@novell.com Status|NEW |NEEDINFO Info Provider| |stbedi@yahoo.com ------- Comment #1 from jg@novell.com 2006-11-21 07:15 MST ------- Please attach /var/log/NetworkManager. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 bernhard.bender@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|stbedi@yahoo.com | ------- Comment #2 from bernhard.bender@web.de 2007-01-14 16:36 MST ------- Created an attachment (id=112923) --> (https://bugzilla.novell.com/attachment.cgi?id=112923&action=view) Excerpt from /var/log/NetworkManager I am not the original reporter of this bug, but I have a similar problem with knetworkmanager. I also use ndiswrapper (for BCM4310) and a WPA PSK protected WLAN. The connect does not always fail The attached log captures two different failures. I can provide more info if needed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 jg@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bernhard.bender@web.de ------- Comment #3 from jg@novell.com 2007-01-15 08:53 MST ------- The log does not contain wpa_supplicant output, hence it's of limited use (Tambet, how can this be possible?). Anyway, there is something interesting in the log: NetworkManager tries to establish the connection twice, the first time with ap_scan 2, the second time with ap_scan 1. For ap_scan 2, the driver may need more information to select the AP, try specifying WPA protocol and ciphers accordingly. And IIRC ndiswrapper does not support per-ssid scanning, so in case your AP is hidden, the "ap_scan 1" attempt will fail. Is your AP hidden? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 ------- Comment #4 from bernhard.bender@web.de 2007-01-16 04:20 MST ------- No, the AP is not hidden. Also, I CAN see the AP's SSID in KNW's menu, as well as my neighbor's AP. wpa_supplianct is the most recent version from their web site. I compiled and installed it in attempt to overcome these problems. I happened again this morning: Boot the machine (an hp compaq nx6325 btw), log in and select the AP in KNW's menu to connect. Connection fails (in phase 2 according to the log). Terminate and restart KNW Try connection again and it works okay. I will provide the log from this morning as soon as I can get them. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 ------- Comment #5 from bernhard.bender@web.de 2007-01-17 03:31 MST ------- Created an attachment (id=113314) --> (https://bugzilla.novell.com/attachment.cgi?id=113314&action=view) NWM log of failed attempt to attach to WLAN This part of /var/log/NetworkManager show a failed attempt to attach to my AP -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 ------- Comment #6 from bernhard.bender@web.de 2007-01-17 03:32 MST ------- Created an attachment (id=113315) --> (https://bugzilla.novell.com/attachment.cgi?id=113315&action=view) NWM log of successful attachment This part of /var/log/NetworkManager shows a successful attachment to the WLAN AP -- 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, or are watching someone who is.
From the log it seem that NWM tries to attach on it own immediatly after log-in, but this fails, possibly due to a missing key (it did not prompt for
https://bugzilla.novell.com/show_bug.cgi?id=222131 bernhard.bender@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bernhard.bender@web.de | ------- Comment #7 from bernhard.bender@web.de 2007-01-17 03:40 MST ------- I have just added two log files from NWM. attachment 113314 shows a failed attempt attachment 113315 shows a successful try. The difference seems to be: The second time a waited several minutes after log-in before trying to attach to the AP. the key or KWallet password). When I try to manually attach while the initial attempt is still in progress, this also fails. When I wait long in enough, it succesds. Note: The WPA key is stored in KWallet, needing a user supplied password to open. I am using OpenSuse 10.2 here. (Maybe product should be changed). Possible the problem is just that NWM does not prompt for a password? The log says: access point 'PbiCDinFh5dXs' is encrypted, and a key exists. No new key needed. which seems to wrong as the machine just booted/user just logged in and KWallet was not yet opened. On second try it asks for a key... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 jg@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jg@novell.com |tambet@ximian.com ------- Comment #8 from jg@novell.com 2007-01-18 03:31 MST ------- Well, if NetworkManager says it has a key, it probably has one. I don't know where it has it got from. Anyway, the log shows that connection attempts with "ap_scan 2" fail while "ap_scan 1" succeeds. As I wrote in comment 3, you need to specify all security specific connection settings to get ap_scan 2 working (that means, WPA protocol and pairwise and group ciphers). You can test it by selecting "connect to other network" and fill in the details. For ap_scan 1 this is not needed, that the reason why it works then. I think NetworkManager could be improved here: First, it is not comprehensible why NM uses "ap_scan 2" in the first place for a non-hidden network. Second, if it really has to set "ap_scan 2", it has to tell wpa_supplicant values for proto, pairwise, and group. Otherwise the driver may be unable to determine the correct AP. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 ------- Comment #9 from bernhard.bender@web.de 2007-01-19 17:27 MST ------- You are right. NWM does have a key. I found that /etc/sysconfig/network/ifcfg-wlan0 had all the information. With this information, NWM tried to connect. Now I changed the if-cfg file: STARTMODE='manual' USERCONTROL='yes' but NWM still tries to connect. Anything else I need to do? Bernhard -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 ------- Comment #10 from bernhard.bender@web.de 2007-01-24 16:10 MST ------- I finally found a solution (workaround?) by removing the wireless LAN network card in the YaST network devices setting. Now NetworkManager no longer tries to connect after boot (it does not know about the interface). Instead, KNM connects (automatically) after Login, which is just an precisely what I wanted. Tired this on two laptops with broadcom (ndiswrapper) and intel (native) WLAN. Since this is not a bug after all, (at least for me using OpenSUSE 10.2), it may well be changes to invalid. Thanks Bernhard -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222131 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #11 from jpr@novell.com 2007-02-07 08:47 MST ------- Closing as per last comment. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com