[hardy] Can't connect to WPA wireless connection using nm-applet

[smarchi]

I can't connect to my WPA-TKIP wireless network using nm-applet. When I try to connect, nm-applet asks me for the password and after I put it, the system tries to connect, but after a while it doesn't do it.

I can only connect to unprotected wireless network, although I haven't tried with WEP networks.

I'm using Ubuntu 8.04 Final Release.

Thanks!

[KeenEars (fl-blade)]

Looks similar to the problem i have. The password seems to be required to be in hex form.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/219964

[Daniel O'Donnell (daniel-odonnell)]

This is a real issue. Which I have confirmed through repeated reinstalls and upgrades from gutsy to various versions of Hardy and derivatives (e.g. Xubuntu, LinuxMint, Ubuntu). It may be related to the issue of the order of modules in the Kernel discussed in the forms surrounding the Broadcom wlan cards, but it is wider-spread. I'm using a INPROCOMM IPN 2220 card and can replicate the problem every time.

Basically the problem is this: when attempting to log onto a WPA protected network in 8.04 and derivatives (either from network manager or the commandline) using ndiswrapper and wpasupplicant, the connection fails. Initial connection is made, but DHCP doesn't seem to provide any reply. In 7.10 with the same versions of ndiswrapper, wpasupplicant, and networkmanager (i.e. loaded from the 8.04 disk in a clean install), the connection proceeds flawlessly.

Since I'm able to replicate the conditions for both working and non-working connections everytime, let me know what you need. I have the impression that this is a major issue that is not showing up in the bug reports as often as you might expect because there is a fix of sorts for Broadcom users and because the problem lies somewhere that is not obvious--i.e. clearly outside of NM, ndiswrapper, and wpasupplicant.

[Guillaume AVRIL (guillaumeavril)]

I'm experiencing this issue from time to time ( ~ every 5 reboot). I need to reboot the computer to make it work again.
I'm using Intel Corporation PRO/Wireless 2200BG wireless card, the 2.6.24-16-generic kernel and nm-applet 0.6.6.
When I read the dmesg output:

ieee80211_crypt: registered algorithm 'TKIP'
ieee80211_crypt_tkip: could not allocate crypto API arc4

I hope that it will help.

[Tank (dan1990)]

This seems to be quite a big problem,

http://tennessee.ubuntuforums.com/showthread.php?s=f3202bbbf70d2ffcbb818426ae343f95&t=964837
http://ubuntuforums.org/showthread.php?t=963379
http://ubuntuforums.org/showthread.php?t=970236

When I select my wireless home network, which uses WPA-PSK encryption, NM tries to connect. It fails and asks for the key to the wireless network. Entering the key sometimes helps, but mostly NM just fails again. The password field contains the hashed value of the key. It correctly shows "Wireless security" to be "WPA & WPA2 Personal".

The issue seems somewhat random, but 98% of all connects fail. This is a clean Ubuntu 8.10 install with all updates. The issue appeared right after the installation, so it cannot have been introduced by an update.

Attached relevant parts of syslog.

[Colin Stark (cstark)]

Assuming that this is the same problem that I'm having, this isn't a problem with network manager at all. I tried Wicd and I've also tried using the command line and I still haven't been able to connect to any encrypted wireless networks (WEP,WPA,WPA2).
I'm using an Intel 2200BG wireless card in an IBM Thinkpad R51. Driver being used is ipw2200.
I have tried connecting to 5-6 different encrypted networks with no success, with all 3 different types of encryption.
I'm running Ubuntu 8.10 with all the latest updates (as of Nov. 25) and if I remember correctly the problem started about a week to two weeks ago. I've been running Intrepid starting with alpha 2 or 3 and I've never had problems up until now. Once the problem started, I haven't been able to connect to an encrypted network once.
I'm not sure if this is a problem with wpasupplicant or with the kernel itself so I'm hoping someone here can figure that out.
Also, network manager seems to be storing the psk instead of the passphrase when it's prompting me for the password, and I have no idea whether this is related or whether this is even a problem at all. Seahorse also has psk's stored instead of passphrases.
Kernel version is 2.6.26-7-generic. Network manager version is 0.7~~svn20081018t105859-0ubuntu1, Wicd version was newest, wpasupplicant version is 0.6.4-2.

For the attached log, I included everything immediately after a new instance of network manager was started. I'd just deleted all the settings about the wireless network it was trying to connect to, so it prompted me for the passphrase which I entered. After failing to connect the first time, it prompted me for the passphrase again, at which point I hit cancel. It also connected to the wired network somewhere in there.

[Alexander Sack (asac)]

this issue should be fixed in jaunty (final NM 0.7); if you still see this, this is most likely a driver issue. Anyway, I will stay subscribed for a while so let me know if jautny is still broken for you for this bug.

[Colin Stark (cstark)]

Fixed on intrepid for me - I have the backports repo enabled so that could be it.
Thanks a lot - this was a big issue for me.

[JoelGrrr (joel-su3analytics)]

"this issue should be fixed in jaunty (final NM 0.7)"

Will NM0.7 work on Hardy?

[discord (colin.williams)]

Doesn't work for me in lucid testing!