Bug 601501 - connecting to secure wireless network fails most of the time.
Summary: connecting to secure wireless network fails most of the time.
Status: VERIFIED FIXED
: 588662 611024 (view as bug list)
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Network (show other bugs)
Version: Milestone 6
Hardware: Other Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Vladimir Botka
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 17:57 UTC by Bart Whiteley
Modified: 2016-04-15 11:41 UTC (History)
2 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/var/log/NetworkManager (25.96 KB, application/x-gzip)
2010-04-30 17:57 UTC, Bart Whiteley
Details
wpa_supplicant.log (399.78 KB, text/plain)
2010-05-06 09:03 UTC, Vladimir Botka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Whiteley 2010-04-30 17:57:50 UTC
Created attachment 358310 [details]
/var/log/NetworkManager

Most of the time, connecting to a secure wireless network with NetworkManager fails.  Occasionally it works, after several tries.  Sometimes countless attempts will yield no success.  If I reboot back into 11.2, I can connect immediately.
Comment 1 Vladimir Botka 2010-05-04 07:54:56 UTC
Thank you for the report. I can reproduce it. The wpa_supplicant does not complete the 4-way handshake. It works fine in 11.2 for me too.
Comment 2 Bart Whiteley 2010-05-04 21:54:29 UTC
Please share a workaround if you come up with one.  This is a really painful bug.
Comment 3 Vladimir Botka 2010-05-05 07:23:55 UTC
(In reply to comment #2)
> Please share a workaround if you come up with one.  This is a really painful
> bug.

You can try to setup traditional ifup/ifdown method in Yast network settings. If you can connect this way then I can help you setup wpa_gui [1].

[1] http://en.opensuse.org/WiFi_HOWTO#wpa_gui
Comment 4 Bart Whiteley 2010-05-05 15:26:16 UTC
I'm guessing that my driver (iwl3945) is not supported by wpa_supplicant. 

I can connect to my home lan (WPA2-personal) with NM.  I can't connect to a work lan (WPA2-enterprise) with either NM or traditional mode.
Comment 5 Vladimir Botka 2010-05-06 09:02:00 UTC
(In reply to comment #4)
> I'm guessing that my driver (iwl3945) is not supported by wpa_supplicant. 
> 
> I can connect to my home lan (WPA2-personal) with NM.  I can't connect to a
> work lan (WPA2-enterprise) with either NM or traditional mode.

Yes, There is a problem with WPA-EAP and the Intel driver(s) in 2.6.33 .

Fresh MS5 installation [1] in runlevel 3 (some X problems in T60) with Intel 3945 [2]. NM is off [3] and  wpa_supplicant configured to connect to the WPA-EAP network. From the wpa_supplicant.conf can be seen that the full EAP authentication did not pass. The same happens most of the time with Intel 5100 [5] and iwlagn driver too, but occasionally the iwlagn connects [6]. The full wpa_supplicant.log is attached to the next comment. Unfortunately, no time to investigate further.

[1] Linux l669 2.6.33-6-desktop

[2] # hwinfo --wlan
<snip>
  Model: "Intel PRO/Wireless 3945ABG [Golan] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4227 "PRO/Wireless 3945ABG [Golan] Network Connection"

[3] # grep NETWORKMANAGER /etc/sysconfig/network/config 
NETWORKMANAGER="no"

[4]
1273130772.086987: RSN: no PMKSA entry found - trigger full EAP authentication
1273130772.087018: wpa_driver_nl80211_deauthenticate
1273130772.095243: No keys have been configured - skip key clearing
1273130772.095260: State: 4WAY_HANDSHAKE -> DISCONNECTED

[5] # hwinfo --wlan
<snip>
  Model: "Intel Wireless WiFi Link 5100"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4232 "Wireless WiFi Link 5100"

[6]
# grep State: wpa_supplicant.log.dat | grep COMPLETED
2010.05.06 11:38:02 State: GROUP_HANDSHAKE -> COMPLETED
2010.05.06 11:38:34 State: COMPLETED -> DISCONNECTED
2010.05.06 11:38:36 State: GROUP_HANDSHAKE -> COMPLETED
2010.05.06 11:39:09 State: COMPLETED -> DISCONNECTED
2010.05.06 11:39:11 State: GROUP_HANDSHAKE -> COMPLETED
2010.05.06 11:40:02 State: COMPLETED -> DISCONNECTED
2010.05.06 11:40:37 State: GROUP_HANDSHAKE -> COMPLETED
2010.05.06 11:40:37 State: COMPLETED -> DISCONNECTED
2010.05.06 11:42:31 State: GROUP_HANDSHAKE -> COMPLETED
2010.05.06 11:43:04 State: COMPLETED -> DISCONNECTED
Comment 6 Vladimir Botka 2010-05-06 09:03:14 UTC
Created attachment 359915 [details]
wpa_supplicant.log

Intel 5100, 2.6.33, WPA-EAP
Comment 7 Bart Whiteley 2010-05-21 16:52:44 UTC
This problem is still present in m7.
Comment 10 Bart Whiteley 2010-05-26 14:55:04 UTC
I tried this suggestion: 
https://bugzilla.redhat.com/show_bug.cgi?id=589777#c2

It did not help.
Comment 11 Vladimir Botka 2010-05-26 22:38:57 UTC
(In reply to comment #10)
> options iwl3945 disable_hw_scan=1
> did not help.

Thank you. This is still work in progress. I suggest to wait until it is ready.
Comment 12 Vladimir Botka 2010-05-27 12:40:12 UTC
*** Bug 588662 has been marked as a duplicate of this bug. ***
Comment 13 Andreas Jaeger 2010-05-27 19:12:10 UTC
I don't understand why this should be kernel related.  I run the 11.3 kernel on 11.2 without problems.  The firmware is in both environments the same (same md5sum).  So, to me it looks like either a compiler issue or a userland issue - but not firmware or kernel in general.

this does not seem to be like the Red Hat bug a issue with heavy load - the system is idle in my case.
Comment 14 Vladimir Botka 2010-05-27 22:45:09 UTC
(In reply to comment #13)

I have enabled debug on iwl3945 and tried to connect WPA-EAP "Novel" network. Packets were sniffed from the air.

I was not able to connect either with NM on channel 44 or on channel 11 with ifup/ifdown. In both cases the iwl3945 driver repeatedly "deauthenticated" with "Unspecified reason"reason=1 .

On channel 44 the AP responded to the "probe request" but the STA did not try to associate. On channel 11 there was no response from the Novell AP to the "probe request" !

This is all I can tell for sure now. To investigate these kind of problems is rather time consuming. I will have to setup WPA-EAP authentication backend on my own and try to reproduce with the WPA-EAP under control.

Just few more notes for the record

(a) "iw list" shows that only passive scanning is allowed on channel 44 

5220 MHz [44] (14.0 dBm) (passive scanning, no IBSS)

(b) https://patchwork.kernel.org/patch/96097/ states:

Some firmware versions don't behave properly when
passive scanning is requested on radar channels
without enabling active scanning on receiving a
good frame. Work around that issue by asking the
firmware to only enable the active scanning after
receiving a huge number of good frames, a number
that can never be reached during our dwell time.

[1] wlan0: deauthenticating from 00:1a:1e:a6:fa:29 by local choice (reason=1)
Comment 15 Vladimir Botka 2010-05-28 14:18:56 UTC
(In reply to comment #13)
> So, to me it looks like either a compiler issue or a userland issue -
> but not firmware or kernel in general.

Would it be possible to try the wpa_supplicant from the "hardware" project ?
Comment 16 Andreas Jaeger 2010-05-31 08:14:31 UTC
Yes, I did - and it worked directly for me!

Please submit to factory and thanks a lot!
Comment 17 Andreas Jaeger 2010-05-31 14:19:39 UTC
submit request 40920
Comment 18 Andrew Jorgensen 2010-06-02 18:39:40 UTC
*** Bug 611024 has been marked as a duplicate of this bug. ***
Comment 19 Vladimir Botka 2010-06-07 10:08:43 UTC
SRID 40920 accepted. Closed as fixed.
Comment 20 Bernhard Wiedemann 2016-04-15 11:41:31 UTC
This is an autogenerated message for OBS integration:
This bug (601501) was mentioned in
https://build.opensuse.org/request/show/40920 Factory / wpa_supplicant