LEAP broken for iwl3945 under hhardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux-ubuntu-modules-2.6.24 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
After upgrade from gutsy to hardy beta, my laptop will not connect to our campus LEAP wireless system.
I have no difficulties connecting to various WEP systems, but the network fails on LEAP.
I have the intel3945 chipset, and have compiled the 1.2.26k iwl3945 module.
Before upgrading, I'd been using knetworkmanager
The same configuration fails to connect under the new update. Knetworkmanager gets to the
28% mark and fails - I get the little popup saying 'Connection Fialure - Could not connect to the
network <name>'.
I've tried Wicd as well, to similar result (although Wicd only has 1 LEAP option).
A colleague with the ipw3945 driver under ubuntu feisty has no problem connecting to the LEAP network using either networkmanager or wicd.
So I understand that the 28% mark is where the leap handshaking/
This would suggest a problem with WPAsupplicant, wouldn't it? dmesg seems to suggest that that is the case:
[ 24.057149] ADDRCONF(
[ 24.172218] wlan0: Initial auth_alg=128
[ 24.172228] wlan0: authenticate with AP 00:11:5c:eb:1a:90
[ 24.173253] wlan0: RX authentication from 00:11:5c:eb:1a:90 (alg=128 transaction=2 status=13)
[ 24.173263] wlan0: AP denied authentication (auth_alg=128 code=13)
[ 24.186905] wlan0: Initial auth_alg=128
[ 24.186915] wlan0: authenticate with AP 00:11:5c:eb:1a:90
[ 24.193500] wlan0: RX authentication from 00:11:5c:eb:1a:90 (alg=128 transaction=2 status=13)
[ 24.193510] wlan0: AP denied authentication (auth_alg=128 code=13)
[ 24.243503] wlan0: authenticate with AP 00:11:5c:eb:1a:90
[ 24.244391] wlan0: RX authentication from 00:11:5c:eb:1a:90 (alg=128 transaction=2 status=13)
But information on wpa_supplicant (http://
I've seen other problems posted with the iwl3945 driver, but haven't seen this particular issue posted yet.
Changed in linux: | |
status: | Unknown → In Progress |
Changed in linux: | |
status: | In Progress → Confirmed |
Changed in linux: | |
status: | Confirmed → In Progress |
Changed in linux-ubuntu-modules-2.6.24: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux: | |
status: | In Progress → Fix Released |
Changed in linux: | |
status: | Fix Released → Confirmed |
Changed in linux: | |
status: | Confirmed → In Progress |
Changed in linux: | |
status: | In Progress → Fix Released |
Changed in linux: | |
importance: | Unknown → High |
Well, here's a bump, if nothing else. I've attached an excerpt from /var/log/syslog showing what networkmanager/ wpa_supplicant are doing.