Bug 1872 - can not connect with WPA2 enabled AP
: can not connect with WPA2 enabled AP
Status: VERIFIED FIXED
: iwlwifi
WPA & WPA2
: iwlwifi-2.6 development tree
: 3945 (Intel(R) WiFi Link 3945) Fedora Core 9
: P1 critical
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-12-24 21:23 by
Modified: 2009-01-06 19:40 (History)


Attachments
wpa2.log (123.05 KB, text/plain)
2008-12-24 21:23, Zheng, Jiajia
Details
Patch: fixing crypto param (2.16 KB, patch)
2009-01-06 12:24, Samuel Ortiz
Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-12-24 21:23:24
Created an attachment (id=1765) [details]
wpa2.log

test environment:
iwlwifi-2.6 commit 2f71382adc117aba10b04e92a464f4404c08aa70
intel 3945 card
iwlwifi-3945-2.ucode 15.28.2.8
IBM-60(Fedora release 9) and SDV (Fedora release 10)

issue:
can not connect with WPA2 enabled AP.
WPA works fine.

steps:
configure AP with WPA2-PSK and AES encrytion.
1. modprobe -r iwl3945
2. modprobe iwl3945 debug=0x43fff
3. wpa_supplicant -Dwext -iwlan0 -c WPA2_PSK_AES.conf
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:1d:70:93:91:70 (SSID='otc-11215947-cisco-2.4g'
freq=2462 MHz)
Associated with 00:1d:70:93:91:70
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Associated with 00:1d:70:93:91:70
WPA: Key negotiation completed with 00:1d:70:93:91:70 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:1d:70:93:91:70 completed (auth) [id=0
id_str=]
4. ifconfig wlan0 192.168.50.166
5. ping 192.168.50.5
From 192.168.50.166 icmp_seq=2 Destination Host Unreachable
From 192.168.50.166 icmp_seq=3 Destination Host Unreachable

We rolled back to commit 9378420a3f8da4acf0a12960dc6a7f531ceb0492, WPA and WPA2
all work fine. 
please read the attached log.
------- Comment #1 From 2009-01-05 15:47:12 -------
*** Bug 1875 has been marked as a duplicate of this bug. ***
------- Comment #2 From 2009-01-06 12:24:23 -------
Created an attachment (id=1773) [details]
Patch: fixing crypto param
------- Comment #3 From 2009-01-06 12:28:17 -------
Thanks for the bug report.

Could you please try the attached patch, as it fixes the problem for me.
It would be really nice if you could run your test once with SW crypto and
another time with HW crypto.
SW crypto is the default behaviour, so you can just run "modprobe iwl3945"
For HW crypto, you'll have to run "modprobe iwl3945 swcrypto=0"

Thanks in advance.
------- Comment #4 From 2009-01-06 19:38:52 -------
Yes. After applying this patch to commit
e98df74b724417607e039a4e0b28ad230e5e9b96, this bug is fixed.

I tried both software/hardware crypto with WPA2 PSK and EAP.
------- Comment #5 From 2009-01-06 19:39:45 -------
Mark as fixed.