[iwl4965] Can't connect to network with IEEE8021X security

Bug #162415 reported by Timo
6
Affects Status Importance Assigned to Milestone
linux-ubuntu-modules-2.6.22 (Ubuntu)
Fix Released
Medium
Tim Gardner

Bug Description

I use a ThinkPad T61 with the build in Intel 4965AGN Wireless card and cant connect a wireless network with IEEE8021X security where PAP is used for the 2 phase authentification. To connect to the network i use wpa_suplicant and got the following logging output.

[snip]

Try to find WPA-enabled AP
0: 00:1b:0c:04:84:70 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1b:53:b9:ff:e0 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:1b:54:8e:6b:f0 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:1b:53:ba:03:10 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:1b:0c:04:85:d0 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
5: 00:1b:0c:04:b5:80 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1b:0c:04:84:70 ssid='fhwmi' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:1b:0c:04:84:70 ssid='fhwmi'
Trying to associate with 00:1b:0c:04:84:70 (SSID='fhwmi' freq=5660 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:1b:0c:04:84:70 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING

[snip]

Dmesg shows the following:

[snip]
[ 817.128000] wlan0: Initial auth_alg=0
[ 817.128000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 817.128000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 817.328000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 817.328000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 817.328000] wlan0: RX authentication from 00:1b:0c:04:84:70 (alg=0 transaction=2 status=0)
[ 817.328000] wlan0: authenticated
[ 817.328000] wlan0: associate with AP 00:1b:0c:04:84:70
[ 817.328000] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 817.328000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 817.328000] wlan0: deauthenticated
[ 817.528000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 817.528000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 830.396000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 830.396000] wlan0: Initial auth_alg=0
[ 830.396000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 830.396000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 830.396000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 830.404000] wlan0: Initial auth_alg=0
[ 830.404000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 830.404000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 830.408000] wlan0: Initial auth_alg=0
[ 830.408000] wlan0: authenticate with AP 00:1b:53:b9:ff:e0
[ 830.408000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 830.408000] wlan0: RX authentication from 00:1b:53:b9:ff:e0 (alg=0 transaction=2 status=0)
[ 830.408000] wlan0: authenticated
[ 830.408000] wlan0: associate with AP 00:1b:53:b9:ff:e0
[ 830.408000] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 830.412000] wlan0: RX deauthentication from 00:1b:53:b9:ff:e0 (reason=2)
[ 830.412000] wlan0: deauthenticated
[ 830.608000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 830.608000] wlan0: RX deauthentication from 00:1b:53:b9:ff:e0 (reason=2)
[ 843.780000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 843.788000] wlan0: Initial auth_alg=0
[ 843.788000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 843.788000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 843.788000] wlan0: deauthentication frame received from unknown AP (SA=00:1b:53:b9:ff:e0 BSSID=00:1b:53:b9:ff:e0) - ignored
[ 843.792000] wlan0: Initial auth_alg=0
[ 843.792000] wlan0: authenticate with AP 00:1b:0c:04:84:70
[ 843.792000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 843.792000] wlan0: RX authentication from 00:1b:0c:04:84:70 (alg=0 transaction=2 status=0)
[ 843.792000] wlan0: authenticated
[ 843.792000] wlan0: associate with AP 00:1b:0c:04:84:70
[ 843.792000] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 843.792000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 843.792000] wlan0: deauthenticated
[ 843.792000] wlan0: authentication frame received from 00:1b:0c:04:84:70, but not in authenticate state - ignored
[ 843.792000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 843.992000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 843.992000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 857.088000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 857.088000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 857.088000] wlan0: RX deauthentication from 00:1b:0c:04:84:70 (reason=2)
[ 857.100000] wlan0: Initial auth_alg=0
[ 857.100000] wlan0: authenticate with AP 00:1b:53:b9:ff:e0
[ 857.100000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 857.100000] wlan0: Initial auth_alg=0
[ 857.100000] wlan0: authenticate with AP 00:1b:53:b9:ff:e0
[ 857.100000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 857.100000] wlan0: RX authentication from 00:1b:53:b9:ff:e0 (alg=0 transaction=2 status=0)
[ 857.100000] wlan0: authenticated
[ 857.100000] wlan0: associate with AP 00:1b:53:b9:ff:e0
[ 857.100000] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 857.104000] wlan0: RX deauthentication from 00:1b:53:b9:ff:e0 (reason=2)
[ 857.104000] wlan0: deauthenticated
[ 857.108000] wlan0: authentication frame received from 00:1b:53:b9:ff:e0, but not in authenticate state - ignored
[ 857.108000] wlan0: RX deauthentication from 00:1b:53:b9:ff:e0 (reason=2)
[ 857.300000] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 857.300000] wlan0: RX deauthentication from 00:1b:53:b9:ff:e0 (reason=2)
[snip]

Cheers

Revision history for this message
Timo (timohirt) wrote :
Revision history for this message
Timo (timohirt) wrote :
Revision history for this message
Christopher Rawlings (rawlinc) wrote :

I see the exact same thing on my Dell D630 laptop at work with an Intel Wireless 4965AGN (on Gutsy 64-bit). I can connect to wireless access points that use 802.11n (5.2 GHz - 5.8 GHz) and either WAP-Enterprise or WAP2-Enterprise with EAP-TLS security settings. When I try to connect to the wireless access points that use IEEE8021X, however, I get the EXACT same errors as reported above in the original bug report. Here is an excerpt from my /var/log/messages followed by more specific information on my wpa_supplicant configurations:

Nov 6 22:08:51 [ 26.177770] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.0
Nov 6 22:08:51 [ 26.177884] iwl4965: Copyright(c) 2003-2007 Intel Corporation
Nov 6 22:08:51 [ 26.178136] ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Nov 6 22:08:51 [ 26.179791] iwl4965: Detected Intel Wireless WiFi Link 4965AGN

Here are two wireless configurations I've tested that produce the errors reported in the original bug report:

NOTE: Also, for reference, I popped in a cheap Linksys pcmcia wireless adapter and verified that these two configurations DO work on different wireless hardware.

Config #1 that produces the errors (wpa_supplicant.conf):

ctrl_interface=/var/run/wpa_supplicant
network={
        ssid="MYSSID"
        scan_ssid=1
        key_mgmt=IEEE8021X
        eap=TLS
        identity="myusername"
        password="mypassword"
        ca_cert="/etc/ssl/certs/myrootcert.pem"
        client_cert="/home/user/certificates/mymachinecert.pem"
        private_key="/home/user/certificates/mymachinecert.key"
        private_key_passwd="mypassword"
        eapol_flags=3
}

Config #2 that produces the errors (wpa_supplicant.conf):

ctrl_interface=/var/run/wpa_supplicant
network={
        ssid="MYSSID"
        scan_ssid=1
        key_mgmt=IEEE8021X
        eap=PEAP
        phase2="auth=MSCHAPV2"
        identity="myusername"
        password="mypassword"
        ca_cert="/etc/ssl/certs/myrootcert.pem"
}

In contrast two the previous two configurations, the following configuration is the only one that works on my Intel Wireless 4965AGN:

network={
        ssid="MYSSID2"
        scan_ssid=1
        key_mgmt=WPA-EAP
        proto=WPA2
        eap=TLS
        identity="myusername"
        password="mypassword"
        ca_cert="/etc/ssl/certs/myrootcert.pem"
        client_cert="/home/crawling/certificates/mymachinecert.pem"
        private_key="/home/crawling/certificates/mymachinecert.key"
        private_key_passwd="mypassword"
}

Revision history for this message
Tim Gardner (timg-tpi) wrote :
Changed in linux-ubuntu-modules-2.6.22:
assignee: nobody → timg-tpi
importance: Undecided → Medium
milestone: none → gutsy-updates
status: New → Fix Committed
Revision history for this message
Christopher Rawlings (rawlinc) wrote :

Tim Gardner, I updated to the official Intel Wireless 4965AGN 1.2.0 module release from your repository (in the thread you list above), but it didn't make a difference with this problem. I was expecting as much though since the issue reported in the other bug you referenced was not at all related to this problem. Do you have any other ideas (or anybody else for that matter)?

Note: For reference, I did verify (through /var/log/messages) that the Intel Wireless 4965AGN 1.2.0 module did load instead of the older 1.1.0 module.

Revision history for this message
Timo (timohirt) wrote :

I updated to 1.2.0 too and still can't connect to a IEEE802.1X protected network.

There is the same issue in Hardy Heron Alpha 3.

I think this is not a Ubuntu only problem and opened a bug at intels bugtracker: http://bughost.org/bugzilla/show_bug.cgi?id=1522

Revision history for this message
Tim Gardner (timg-tpi) wrote :

iwlwifi 1.2.0 is golden.

Changed in linux-ubuntu-modules-2.6.22:
status: Fix Committed → Fix Released
Revision history for this message
Jaco (jacotb) wrote :

I'm having the same problem.

Revision history for this message
jarlostensen (ubuntu-jarlostensen) wrote :

I have the same type of problem with an Intel 5300 AGN card in my Dell Laptop.
The router is a LiveBox (the Orange proprietary type where you have to let it enter a "pairing mode" to accept connections) and I have not had any trouble connecting to it with either the same laptop when I boot it into Windows 7 or another laptop running Ubuntu 8.10 (albeit with a different network card.)
I have not tried the Intel drivers mentioned in this thread yet.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.