LEAP broken for iwl3945 under hhardy

[Charlie Figura]

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/NetworkManager and had successfully been able to connect to the LEAP network via the WPA Enterprise/ LEAP IEEE 802.1x, WPA1 version.

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/authentication is being done.
This would suggest a problem with WPAsupplicant, wouldn't it? dmesg seems to suggest that that is the case:

[ 24.057149] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 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://hostap.epitest.fi/wpa_supplicant) states that wpasupplicant supports LEAP: "* (note: requires special support from the driver)". This suggests to me that the problem lies with iwl3945.

I've seen other problems posted with the iwl3945 driver, but haven't seen this particular issue posted yet.

[Charlie Figura (cfigura)]

Well, here's a bump, if nothing else. I've attached an excerpt from /var/log/syslog showing what networkmanager/wpa_supplicant are doing.

[Leann Ogasawara (leannogasawara)]

Hi Charles,

I noticed you mention you have compiled and are running the newer 1.2.26k version of the module. I also see you posted a comment to the upstream bug report as well which is great. http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1522 . I'm just adding an upstream bug watch from this report to that one. Thanks.

[ubuntu_demon (ubuntu-demon)]

The bug I reported is similar :
https://bugs.launchpad.net/linux/+bug/220640

[J. J. Ramsey (jjramsey)]

I found that LEAP *used* to working under Gutsy, stopped working under Gutsy, and still doesn't work under Hardy. And this is all with the same university wireless system. What's odd is that under Hardy, I don't even get the applet icon indicating that it's trying to connect.

[J. J. Ramsey (jjramsey)]

I compiled a 2.6.25.3 kernel on Ubuntu, which has the latest stable iwl3945 driver, and this fixed the wireless problem for me. Obviously, that's a lousy permanent solution, but it indicates (1) that the upstream fix worked, and (2) that the problem can be solved with an appropriately patched kernel.

[Leann Ogasawara (leannogasawara)]

Care to test the Intrepid Ibex 8.10 kernel? It was most recently rebased with the upstream 2.6.25 kernel and is currently available in the following PPA:

https://edge.launchpad.net/~kernel-ppa/+archive

If you are not familiar with how to install packages from a PPA basically do the following . . .

Create the file /etc/apt/sources.list.d/kernel-ppa.list to include the following two lines:

deb http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main
deb-src http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main

Then run the command: sudo apt-get update

You should then be able to install the linux-image-2.6.25 kernel package. After you've finished testing you can remove the kernel-ppa.list file and run 'sudo apt-get update' once more. Please let us know your results. Thanks

[Charlie Figura (cfigura)]

Leann -

Unfortunately, the 2.6.25-1 kernel package didn't help. I installed linux-image-2.6.25-1-generic and linux-ubuntu-modules-2.6.26-1-generic. When i do an iwconfig, there are no wireless extensions *at all*.

I've attached the relevant portions of the dmesg output.

Any ideas?

[J. J. Ramsey (jjramsey)]

> Any ideas?

Do you have the microcode for iwl3945 installed where the driver can find it? It should be in, IIRC, /lib/firmware/`uname -r` or something like that.

[Charlie Figura (cfigura)]

In /lib/firmware/2.6.25-1-generic I find:
iwlwifi-3945-1.ucode
iwlwifi-3945.ucode
as well as for the 4965. It looks like the same files as under my 2.6.24-17-generic directory.

So, I guess, yes, I do have the microcode installed. I didn't do anything in particular on that front - it should have been installed there by the deb package, right?

[derwiki (derewecki)]

I'm in the same boat as charles.figura. I built a new kernel per the instructions at:

https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

which build 2.6.26-rc5-custom. I can boot to this kernel, but I have no wireless extensions. There was no /lib/firmware/2.6.26-rc5-custom, so I copied /lib/firmware/2.6.4.19-generic to /lib/firmware/2.6.26-rc5-custom and rebooted. I didn't know whether that would work, but I figured it was worth a try -- turns out that it doesn't work.

Also, per Leann Ogasawara's instructions, I tried adding the PPA repo and updating, but apt couldn't find the correct packages. Also, when doing apt-get update, the launchpad lines were preceded with Ign instead of Hit -- not sure if that makes a difference.

Any help would be greatly appreciated!

[derwiki (derewecki)]

Does "Status: Fix Released => Confirmed" mean anything ?
I just grabbed all the updates that I could today, and I still can't connect to a LEAP network.

Also, just to follow, it seems that Charles has been following up with the Intel-Wireless team, and there is more info there:
http://intellinuxwireless.org/bugzilla/show_bug.cgi?id=1522 (same link as above)

[Dominic Evans (oldmanuk)]

I tried booting from yesterday's brand new Intrepid Ibex Alpha 3 live cd and connecting to LEAP at work using iwl3945. It is _still_ broken ;-(

[zedic (zedic)]

I recently moved to ubuntu 8.04 from Fedora on my Lenovo T60. Wireless worked great under Fedora core 9. I can not connect to my LEAP IEEE 802.1x network with Ubuntu 8.04. I have the latest stable updates. I have tried using NetworkManager with no luck. I tried using my wpa_supplicant.conf that worked in Fedora with no luck. I've already put a lot of time into my Ubuntu setup. I hope this is resolved soon, because I'd rather not go back to Fedora.

Lenovo T60
Intel PRO/Wireless 3945AGB
iwl3945

[Dominic Evans (oldmanuk)]

excellent news!

I upgraded to Intrepid Ibex Alpha 4, which has now moved to NetworkManager 0.7, and LEAP is now working for me \o/

[pepe123 (ferrer123)]

It will not work for me.
I do not understand as we have changed IPW, which functioned well in iwl that is not sufficiently tested.
The wifi in a laptop is something very basic.
Pepe123

[zedic (zedic)]

!WORKS WITH UPDATES FROM TODAY!

I upgraded to Intrepid Ibex Alpha 4 some time ago. It still didn't work for me until today. I have been running update-manager every day and installing the latest updates. LEAP with Dynamic WEP keys works for me with the updates from today!!!!

Lenovo T60
Intel PRO/Wireless 3945AGB
iwl3945

Thanks!

[zedic (zedic)]

I upgraded to Intrepid Alpha 5, and now it seems to be broke again.

[derwiki (derewecki)]

LEAP is working for me in Intrepid Alpha 5 (on a T61), mostly. Wired and wireless seems a little flakier than normal -- but LEAP -does- authenticate.

[Leann Ogasawara (leannogasawara)]

Beginning with the Intrepid Ibex release the linux-ubuntu-modules package was actually merged with the linux kernel source package. As a result I'm adding the 'linux' task so that we continue to monitor this for Intrepid. It seems like we are getting some positive feedback regarding recent Alpha testing. Note that Alpha5 contained a newer 2.6.27 kernel.

charles.figura, since you are the original bug reporter, would you be able to test the latest Alpha5 - http://www.ubuntu.com/testing/intrepid/alpha5 and let us know your results. Thanks.

[Charlie Figura (cfigura)]

So I've tested intrepid alpha5, and I'm still not getting LEAP connectivity under for my iwl3945. Using network-manager, I've gotten the following results:

Using the direct LEAP setting, dmesg reports:
[ 279.949236] wlan0: authenticate with AP 00:11:92:5a:d4:90
[ 280.148097] wlan0: authenticate with AP 00:11:92:5a:d4:90
[ 280.348081] wlan0: authenticate with AP 00:11:92:5a:d4:90
[ 280.548067] wlan0: authentication with AP 00:11:92:5a:d4:90 timed out
<4 lines repeat>

Using the WPA-Enterprise -> LEAP setting, network-manager crashes:
[ 444.452851] nm-connection-e[8416]: segfault at 6c620069 ip b7386742 sp bff694c0 error 4 in libglib-2.0.so.0.1707.0[b732d000+b5000]

Manually, I'm having problems. I picked up a USB network stick (zd1211) that works GREAT under wicd and network-manager on my hardy installation. I'd been trying to run wpa_supplicant manually, while the zd1211 works under wicd and network-manager, I can't get EITHER the zd1211 OR the iwl3945 working using the manual wpa_supplicant configuration, on EITHER hardy OR intrepid.

If someone can give me some input on the configuration file, I'd be most grateful.
My current configuration is attached, if anyone can give some advice. Do I need to kill networking (or network-manager or wicd) before using manual configuration?

A few other notes - I don't have a group 'wheel', so someone (on launchpad) had recommending setting ctrl_interface_group=0.

If there's anything else goofy that's inhibiting me, that I'm messing up here, please let me know.

But in any case, LEAP is still not working out-of-the-box using network-manager.

[Dominic Evans (oldmanuk)]

are you testing this on clean installs / livecd boots of intrepid?

my iwl3945 on a Thinkpad T60p is working flawlessly with NM 0.7

[Charlie Figura (cfigura)]

This is on an intrepid alpha 5 livecd.

[Cerebrate (robojoos)]

I'm using hardy upgraded to Intrepid (via update-manager -d).

Toshiba A135-S4467 Laptop, using iwl3945.

Previously, I also had the same problem, being unable to connect to my campus' LEAP/Wpa-Enterprise network as soon as I upgraded to hardy. Upon upgrading to Intrepid, and using kernel 2.6.27-2, along with NetworkManager 0.7, LEAP and WPA Enterprise now work, as I am able to connect to the campus' wireless now.

Attempting to use Hardy with an upgraded kernel did not work. I believe this has something to do with also using NetworkManager 0.7

So yes, this is fixed with Intrepid for me.

[Charlie Figura (cfigura)]

I've tried the intrepid alpha 5 and not alpha 6, and I'm still not having any luck.
Under alpha 6, I'm getting the same timeout error I was before:

wlan0: authenticate with AP 00:11:92:5a:d4:90
wlan0: authenticate with AP 00:11:92:5a:d4:90
wlan0: authenticate with AP 00:11:92:5a:d4:90
wlan0: authentication with AP 00:11:92:5a:d4:90 timed out

Here's the odd thing - I'd picked up a belkin USB wifi stick ("zd1211") to do LEAP on my hardy system, and it works great. But under alpha 5 and 6, I can't get it to work either - same timeout error messages.

So I'm wondering if there's a different problem here. Is there a timeout setting that could be adjusted?

[Leann Ogasawara (leannogasawara)]

Hi charles,

I assume this is still an issue for you with Intrepid' final release? For now we'll keep this open against the actively developed linux kernel but against linux-ubuntu-modules-2.6.24 this will be closed per the SRU policy - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

[Charlie Figura (cfigura)]

Fabulous. Between the iwl3945 still not working for LEAP and the fact that knetworkmanager isn't working for LEAP, it's somewhat amazing that intrepid could actually have been allowed to be released.

I guess I just don't understand how a version can be released when it's got serious flaws. Particularly when it *used* to work (under ipw3945).

Sorry, I hate to vent, but I've been without decent networking (carrying a stupid ethernet cable around with me wherever I go on campus) for six months now. I've reinstalled, upgraded, reinstalled, tried *everything* anyone could tell me to do. I've tried different machines, for crying out loud, to make sure I didn't have a hardware problem.

Still fails. *sigh*

[Dominic Evans (oldmanuk)]

Unnecessary/disgraceful tone of language considering that this works flawlessly for many people.

[Charlie Figura (cfigura)]

I apologize for my tone and frustration. I certainly don't have anything like a service contract, and I have no right to take my frustration out on people in this forum. I do appreciate the work that the developers do.

I had not been under the impression that I was the only one who was having this difficulty, but apparently there's something bizarre going on here locally. It's unfortunate that no one's been able to recommend anything that's helped the situation, but that's not the fault of this forum.

My apologies, I won't let it happen again.

[Cerebrate (robojoos)]

LEAP works for me in Intrepid. Has been doing so for a while - https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/209920/comments/23

[Charlie Figura (cfigura)]

One last attempt? I know that this bug is filed under iwl3945 for hardy, but here's my situation.
No LEAP works for me at all, under gnome-applet, knetworkmanager, or wicd on Intrepid, whether I'm using the built-in iwl3945 or the USB dongle (that had worked fine under Hardy, but no longer under Intrepid).
I've tried the dongle on different machines using the Live Intrepid Ubuntu cdrom. No joy - always the SAME result, authentication time out.

Colleagues are currently using LEAP under Gutsy (using the ipw3945 driver) and under Hardy (using the dongle).

So if no one else but me is having trouble with LEAP under Intrepid, then how has our IT department screwed up the LEAP configuration that's so unforgiving to Intrepid? Our IT is completely linux-hostile, so it's up to me to solve this problem, they won't help at all.

Any recommendations, any, will be greatly appreciated.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Leann Ogasawara (leannogasawara)]

Closing the launchpad bug per Charles' comment posted in the upstream bug:

http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1522#c80

"It is working under networkmanager now. NOT working under knetworkmanager or
networkmanager plasmoid, but that seems to be a problem with that code, not
with the driver."