[iwlagn] networkmanager applet cannot connect to WPA2 home network. Neither can WICD.

this is a critical bug in plasma network manager applet. it doesnt answer requests for secrets. meaning: it doesnt work for anything but open wifi networks.

ok, could be just that user submitted the syslog snippet when he cancelled attempt. i will debug that with him on IRC later. stay tuned.

Also, the laptop can't connect in ubuntu (gnome).

I added new syslog.ubuntu

Added new syslog

I used tha plasma applet

Complete kubuntu syslog added

indeed most likely a driver issue.

Bug reported upstream here: http://bugzilla.kernel.org/show_bug.cgi?id=12958

Keeping bug importance, and noting its been sent upstream can be marked as triaged.

I'm also having the same problem, after upgrading from Intrepid to Jaunty.
How can I help?

FYI, if it helps, I'm seeing the same issue on 2 laptops.

First laptop has an Intel PRO/Set 2200, that was a fresh install with Kubuntu jaunty from cd not more than a week ago, but fully updated as of today via wired connection.

Second laptop has an Intel PRO/Wireless 3945ABG, this was an upgrade from Intrepid to Jaunty. This one is also fully updated as of 10 mins ago, via wired connection.

This issue is not present in kernel 2.6.28-9-generic. It appears as if it was introduced in 2.6.28-10-generic. I also have an intel 3945 wireless card. Attatched is a snippet of my syslog, kernel daemon logs when trying to connect to my wireless lan at home w/ both WEP and WPA2 on Kernel 2.6.28-11-generic. Also I don't know if it will matter but I am running 64bit. It is a dell inspiron 1525n. If there is anything else needed please let me know.

I had a similar problem when I upgraded from hardy to intrepid on my fonero router.
I reported the problem here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963
Now I'm using a different router.
It was never solved.

My router is a Thomson tg784 and it's not connect to fonero.

This is also affecting enterprise WPA2 networks. My university uses WPA2 with PEAP auth.

Hello ryan,

yes, but there is already another bug about WPA Enterprise networks: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963

We can focus here in the WPA personal networks.
If we are more specific is more easy to found the cause of the problem

I'm using the ath5k driver for Atheros AR242x card on 2.6.28-11-generic from Jaunty with the same issue. Its an ASUS F5 notebook.

This in syslog when trying to initiate a connection:

Mar 31 23:05:57 aether-laptop NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service

I'd have sworn I was using a different driver on Intrepid, maybe I blacklisted and used ndiswrapper... Anything I can do to help?

Ubuntu Intrepid Ibex (x86_64), network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61). Same problem with WPA Enterprise.

Javier,

Thank you. I understand the idea but would point out that WPA2
regardless of enterprise or personal is not working with what appears
a specific chipset. From what I understand, while obvious differences
between something that is enterprise grade and home/small office WPA2
its still WPA2 and the basics with its functionality is the same. And
I would advise that the two bugs be merged.

-Ryan

2009/3/31 Javier Jardón <email address hidden>:
> Hello ryan,
>
> yes, but there is already another bug about WPA Enterprise networks:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963
>
> We can focus here in the WPA personal networks.
> If we are more specific is more easy to found the cause of the problem
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Good news!

Today I can connect to my home WPA2 / AES network. Works in Ubuntu and Kubuntu.
I attach kubuntu syslog.

Added ubuntu syslog: syslog_ubuntu_works

Ok,

I can connect to my WPA2 network but after computer suspend I can't.

syslog_after_suspend_ubuntu attached

Seems to be fixed for Javier. ryan, can you confirm on latest Jaunty?

Alex, https://bugzilla.redhat.com/show_bug.cgi?id=388471 says that this was fixed in upstream NetworkManager. Javier says it's fixed for him. Can you please change the tasks/close as appropriate? Thank you!

I still can't connect to both of my wireless routers (Thomson tg784 and La Fonera) using WPA.
If I reboot them, I'm able to connect to them, almost instantly. After that, I'm unable to connect again.

Martin

I can confirm that the bug is still present even after the latest
updates (which i did not see networkmanager listed for update).
Rolling back to kernel 2.6.28-9 is the only work around that i have
found to work for my situation right now. My home router is a linksys
WRT-54GL at University it is Cisco based w/ PEAP and MSCHAPv2 for
inner auth. method.

-Ryan

On Wed, Apr 1, 2009 at 04:32, jmachado <email address hidden> wrote:
> I still can't connect to both of my wireless routers (Thomson tg784 and La Fonera) using WPA.
> If I reboot them, I'm able to connect to them, almost instantly. After that, I'm unable to connect again.
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

this bug was a driver bug which seems to be fixed now. Its been reported as fixed in bug 329798 too as it seems; NM certainly didnt change anything in the last rounds that could have fixed this.

When is the patched driver in the kernel going to be released? As of
this morning with the latest updates I am unable to connect to any
WPA2 Personal/Enterprise Network. The only solution has been to roll
back to 2.6.28-9 as both 2.6.28.-10 and 2.6.28-11 are broken.

On Wed, Apr 1, 2009 at 09:31, Alexander Sack <email address hidden> wrote:
> this bug was a driver bug which seems to be fixed now. Its been reported
> as fixed in bug 329798 too as it seems; NM certainly didnt change
> anything in the last rounds that could have fixed this.
>
> ** Changed in: plasma-widget-network-manager (Ubuntu Jaunty)
>       Status: Triaged => Invalid
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

What is critical about this? It doesn't appear to be an issue any longer.

Javier, regarding comment 25, "I can connect to my WPA2 network but after computer suspend I can't." (https://bugs.edge.launchpad.net/ubuntu/+bug/348275/comments/25), could you open a new bug report for that issue?

Also, per a request from the release team, we will reopen this bug as it is fixed from some but not everyone. Thanks.

This is still a problem for some users:
HW:
    description: Notebook
    product: HP Pavilion dv7 Notebook PC
    vendor: Hewlett-Packard
    version: 1
    serial: xxxxxxxxxx
    width: 64 bits
    capabilities: smbios-2.4 dmi-2.4 vsyscall64 vsyscall32

 ~$ uname -a
   2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 04:39:54 UTC 2009 x86_64 GNU/Linux

 ~$ dmesg | grep ath5k
[ 15.231457] ath5k_pci 0000:09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 15.231470] ath5k_pci 0000:09:00.0: setting latency timer to 64
[ 15.231558] ath5k_pci 0000:09:00.0: registered as 'phy0'
[ 15.372371] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[ 30.535823] ath5k phy0: gain calibration timeout (2412MHz)
[ 30.535827] ath5k phy0: can't reset hardware (-11)
[ 30.907197] ath5k phy0: gain calibration timeout (2412MHz)
[ 30.907202] ath5k phy0: can't reset hardware (-11)

 ~$ sudo lshw
*-network DISABLED
    description: Wireless interface
    product: AR242x 802.11abg Wireless PCI Express Adapter
    vendor: Atheros Communications Inc.
    physical id: 0
    bus info: pci@0000:09:00.0
    logical name: wmaster0
    version: 01
    serial: xx:xx:xx:xx:xx:xx
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless ...

Just made a discovery that seems strange but could be unrelated:
From the dmesg output:
[ 15.231457] ath5k_pci 0000:09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
 And when checking with:
sudo lspci -vvnn:
09:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
        Subsystem: Hewlett-Packard Company Device [103c:137b]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 128 bytes
        Interrupt: pin A routed to IRQ 18
!!! Last line could be important when comparing with video:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4]
        Subsystem: Hewlett-Packard Company Device [103c:30fc]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 18

Looks like an IRQ conflict but it is maybe not important.......

I have the same problem with Atheros AR242x and ubuntu jauntly UNR with the last updates. If you want I can give you all info you need

this is happening to me as well, was working with 2.6.28-11.39... but in 11.40 it is unable to connect.

I dist-upgraded from intrepid to jaunty, and check daily for new updates... WPA broke on me yesterday, so now it is back to the good old Adamm's kernel :(

I am still able to use the network with other computers, and also can get onto unsecure networks.
Using an RaLink RT2860

I suggest this might actually be an issue with wpasupplicant. I cannot do a connection with that either.

This is my output when trying to connect with wpa_supplicant - my key was generated with wpa_passphrase.

aether@aether-laptop:/etc$ sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:14:6c:69:1d:ce (SSID='WirelessAP' freq=2462 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:14:6c:69:1d:ce (SSID='FancyPantsJane' freq=2462 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory

FYI, I have two PCs using different cards with the issue, one with an Atheros AR5001X+ and the other with an Atheros AR242x, I have Jaunty_Proposed in my repository and all up to date. Both can connect to open or WEP protected networks.

I did a search for bugs in wpasupplicant on launchpad but couldn't find a relevant one. I can start attaching random log files if it will help? Does network manager just use wpasupplicant? If so, I suggest this would be a critical bug there.

I would like to confirm that I've been experiencing this same bug on my laptop with an Intel PRO/Wireless 5100 AGN controller.

After resuming from suspend, I would not be able to connect to a WPA2 network (WPA2-PSK).

When I unloaded and reloaded the wifi module, iwlagn, I was then able to connect to the wpa2 network.

This was the messages found in dmesg when failing to connect:

wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
wlan0: authenticated
wlan0: associate with AP XX:XX:XX:XX:XX:XX
wlan0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x1 status=10 aid=0)
wlan0: AP denied association (code=10)

Nope. Just updated Jaunty on my laptop fully and removed WICD and installed plasma-widget-network-manager. Rebooted and added the widget to the desktop.

Intel PRO/Wireless 3945ABG.

Doesn't offer WPA2 as an option. WICD works fine. Now I need to go find my wire and reinstall WICD.

I'm getting the WPA2-Enterprise error as well, with the latest version of Kubuntu Jaunty. Using the plasmid, not sure what else to do. Seems to never connect.

Just to kick in - Ubuntu Jaunty w/ full updates and still no connect
for my intel 3945 card. When I'm around the laptop again I will pull
syslog, kernel log message and wpa_supplicant from boot forward.

-Ryan

On Fri, Apr 10, 2009 at 14:23, Joe <email address hidden> wrote:
> I'm getting the WPA2-Enterprise error as well, with the latest version
> of Kubuntu Jaunty. Using the plasmid, not sure what else to do. Seems to
> never connect.
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network (intel 4965)
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have the same problem.

I have an IBM thinkpad x31. I get the following error in my syslog:

wrede@erik:~$ dmesg | grep ath5k
[ 11.706922] ath5k_pci 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 11.707027] ath5k_pci 0000:02:02.0: registered as 'phy0'
[ 11.859671] psmouse serio1: ID: 10 00 64<6>Registered led device: ath5k-phy0::rx
[ 11.909219] Registered led device: ath5k-phy0::tx
[ 11.909225] ath5k phy0: Atheros AR5211 chip found (MAC: 0x42, PHY: 0x30)
[ 11.909229] ath5k phy0: RF5111 5GHz radio found (0x17)
[ 11.909232] ath5k phy0: RF2111 2GHz radio found (0x23)
[ 128.647856] ath5k_pci 0000:02:02.0: PCI INT A disabled
[ 730.984775] ath5k_pci 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 730.984983] ath5k_pci 0000:02:02.0: registered as 'phy2'
[ 731.021697] Registered led device: ath5k-phy2::rx
[ 731.021719] Registered led device: ath5k-phy2::tx
[ 731.021724] ath5k phy2: Atheros AR5211 chip found (MAC: 0x42, PHY: 0x30)
[ 731.021728] ath5k phy2: RF5111 5GHz radio found (0x17)
[ 731.021731] ath5k phy2: RF2111 2GHz radio found (0x23)

I have the same problem, but different behavior.

The NetworkManager applet can connect to WPA2 home network, but it get disconnected for every several seconds. And then the whole system does not response any more(can't even switch to other tty console). Have to power off the laptop to restart it.

My laptop is an Lenovo Thinkpad T61. Just updated to the latest Jaunty this morning.

$ uname -a
Linux Ubuntu-T61 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

PS: attached syslog. Thanks.

Also attached dmesg and lspci result. Hope this will help identify the root cause. Thanks.

$ lspci

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HBM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
03:00.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b6)

I can confirm the same bug. After updating to Jaunty and I can only connect to Open networks. Chipset is Intel 4965. This goes for Plasma widget and knetworkmanager. Knetworkmanager does not even react when I click a WPA network. Usually you see at least some activity trying to connect to the network.

I have Acer laptop with kubuntu jaunty (beta):

Intel Corporation PRO/Wireless 4965 AG or AGN

and had failures connecting to any wireless except open ones, then installing:

aptitude install linux-backports-modules-jaunty-generic

resolved at least WPA2 connection problem, so this seems to be driver issue.
(btw. modules-package fixed also my eeepc ath5k problems)

I did a fresh install of Kubuntu Jaunty beta on my ThinkPad X40 (and updated every day). In the beginning (with Jaunty beta) I was able to connect to my home network (WPA). For a few days now I get a connection (NM plasmoid shows that I have an IP) but I still can not connect to the Internet.
Open networks kind of work. I can connect and get internet. But the Wifi networks don't seem to get rescaned. If I change location (even to another Hotspot within same Network SSID) or after waking from sleep I have to reboot to get the WLAN to connect.

If I can help with resolving this issue let me know how.

I can confirm this with Intel 3945ABG in Dell notebook connecting to FreeBSD 7.1 router using WPA2/AES. Works fine with Kubuntu Jaunty Beta (kernel 2.6.28-11 #37). Doesn't work with Jaunty RC (kernel 2.6.28-11 #41). On RC, wpa_supplicant.log contains nothing other than "CTRL-EVENT-SCAN-RESULTS" entries. Also, on Beta the KDE wallet gets opened to remember the password, but it doesn't on RC.

Graham

I just tested the final version Gnome LiveCD and the bug is still there. My old Thinkpad T41 with ipw2100 cannot connect to my WPA2 protected home wlan, while Ibex has been working flawlessly.

Yep. Doesn't work on the release of Kubuntu Jaunty live CDROM either. I'll install over the weekend and see if I can find the problem.

Graham

I can confirm the bug concerning NetworkManager and WPA2 on Kubuntu Jaunty upgraded from Intrepid.
However i managed to connect using wpa_supplicant in command line after killing NetworkManager so that it frees the device.

Hardware : Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Kernel : 2.6.28.11.15

Wpa_supplicant trace :
1240580521.965781: CTRL-EVENT-SCAN-RESULTS
1240580521.965871: Trying to associate with 72:xx:xx:xx:xx:38 (SSID='my_essid' freq=2417 MHz)
1240580521.982751: Associated with 72:xx:xx:xx:xx:38
1240580523.530673: WPA: Key negotiation completed with72:xx:xx:xx:xx:38 [PTK=CCMP GTK=TKIP]
1240580523.530717: CTRL-EVENT-CONNECTED - Connection to 72:xx:xx:xx:xx:38 completed (auth) [id=0 id_str=]

This may SOLVE the problem for KDE 4.2 under Jaunty:

I can also confirm this bug while trying to connect to a WPA2-PSK encrypted network (Fritz!Box) with my Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) (Thinkpad T60)

My syslog showed to following entry when trying to connect:
NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service “

After searching the web for a while I found the solution for KDE 4:
1. Close any open knetworkmanager
2. Remove any open Networkmanager plasma-widget
3. Stop Networkmanager (sudo /etc/init.t/Networkmanager stop)
4. Open your favorite package manager and remove knetworkmanager (mainly to prevent it from starting while rebooting and to save disk space as it is not needed any more)
5. Start Networkamanger again (sudo /etc/init.t/Networkmanager start)
6. Add the Networkmanager plasma-widget again to your desktop

Probably you have to reboot or at least log off and log in again.

If you prefer knetworkmanager, remove the plasma-widget instead to prevent ist from starting anything with KDE. This should also do the trick.

Networkmanager seems to get into trouble when being used with to frontends at the same time and KDE seems to start something from the plasma-widget (if installed) even if it is not placed on your desktop.

Adding something to the plasma-widget-network-manager and knetworkmanager packages marking them as conflicting would also solve this for anyone not reading this :-)

Starting kwalletd fixes the problem for me here.

I'm working with linux-backports-modules-jaunty-generic package installed from the repository.

What is weird is that WICD works when knetworkmanager and the kde4 plasma widgets did not.

I'm working with linux-backports-modules-jaunty-generic package installed from the repository.

What is weird is that WICD works without the package when knetworkmanager and the kde4 plasma widgets did not.

Similar issue here 2.6.28-11-generic didn't work, even using iwconfig to setup network... 2.6.27-11-generic works OK, so i think is something kernel related more than network, userland or other things.

all with 9.04 upgraded from 8.10

Confirmed. I have HP nx7400 with Intel 3945 and Linksys WRT54GC. Latter has been set up to WPA2-PSK and works fine when I'm under Windows, but do not work at all when I am under Jaunty. Please fix it, wires and Windows makes me nervous.

Same problem here on my Dell XPS M1530 with Intel Corporation PRO/Wireless 4965 card. Let me know if you still need logs or other technical info.

I have to withdraw my comment from 23.04. I can no longer reproduce the issue.

This now seems to work correctly. I didn't notice any system updates that might have been relevant so I don't understand how it was fixed. But it is...

... except for one thing. I need to type my WPA2 password each time I connect. Even though kwallet gets opened to remember the password, it doesn't seem to use it next time. I have to enter it again. Kwallet isn't opened until after the password is entered so it can't get it from there.

It works in my ubuntu 9.04(Jaunty) now.

As mkuutti commented before, I installed linux-backports-modules-jaunty-generic.

Thanks.

I'm using jaunty release, fresh install, with an Intel Wifi Link 5100 card (Asus N50Vn notebook) and linux-backports-modules-jaunty-generic fixed WPA2 auth for me. Thanks.

Installing linux-backports-modules-jaunty-generic apparently fixed WPA2 for me as described above.

One may however wonder about the need for installing "backported" modules less than a week after the Jaunty distribution was released...

KDE 4.2's NetworkManager plasmoïd is definitely buggy anyway :

- It only shows an option for "WPA", not "WPA2", event though after installing backported modules this will allow connecting to a WPA2-only AP.

- Even though the network password have been "saved" (using KDE Wallet), the plasmoïd will stubbornly ask to manually type the network password again in at least 2 situations:
a/ When manually changing from a wireless net to another (even though both networks have been duly registered with their respective passwords).
b/ When, at KDE startup, I'm prompted for the Kdewallet password for getting the network key. If I don't type it quickly enough (i.e. I was away from the machine while KDE was starting up), then the plasmoïd will request the network password by itself (and the 1st connection attempt will subsequently fail anyway)
c/ In the situation where the network plasmoïd asks several times for the password, it will duplicate each time the same network entry in its "connection list", so you end up with a "connection list" containing 10 times the same net...
d/ Sometimes displays the name of the currently connected network, sometimes not. When it does it shows (at least in french) : "xxxConnecté à « somenetworkname »" the "xxx" being actually displayed, ooks like a string placeholder that was forgotten there...

Well, the KDE Network plasmoïd is currently so buggy and it is so obvious that I wonder if it's really worth describing it...

Following the advice people have given here, I installed linux-backports-generic yesterday and tried my wireless again. At first it didn't seem to help, but after I went into System Settings/Network and deleted all the duplicate copies of my network definitions, I was able to connect. So thanks to everyone who has contributed ideas on this.

I have to agree with Swami Petaramesh: the idea of the Network Manager plasmoid is nice, and it's reasonably pleasant to look at, but the implementation leaves a lot to be desired. Aside from the failure to connect (and the lack of feedback about failure to connect), the problems in its interaction with KWallet are really annoying. I don't want to have to memorize the security key for my network, but in effect that's what I have to do currently because it keeps prompting me for it even though it's been saved (or should have been) to the wallet. The duplication of network entries is infuriating too. Also, for one of my networks, I filled in the BSSID to connect to, but that never seems to be remembered.

Another problem that I've noticed is that if I change the number of wireless networks to display (in the plasmoid's settings), the size of the plasmoid's popup does not change, and there is no scroll bar. So increasing that number beyond 4 is basically useless.

I still have this problem on my Dell XPS M1330 with and without linux-backports-modules. For my case, removing iwlagn and re-add it solved the problem. I checked /var/log/wpa_supplicant.log and found

No configuration found for current AP.

When WPA2 joining is failed. When remove and re-add driver, this line never appeared again on the log.

I installed the backports-modules as described. It is still not working for me with WPA-EAP (PEAP) MS-CHAPv2 ..............

This works fine in ubuntu 9.04, after many years of using linux why are there these problems still finding their way into final releases? Absolutely ridiculous these things break for release to relase, and between version of the same release ubunt/kubuntu.

I'm puzzled !

WPA2 support in Jaunty with KDE network plasmoïd "suddenly started working" on 2 machines after I just rebooted them, without having applied updates yet !

- An Acer Aspire 3104WLMi using the ath5k module
- A Dell XPS M1330 using the iwl3945 module

I have not installed the backport modules on any of these 2 machines...

They now happen to have WPA2-AES working... (AP is a Linksys WRT54G running DD-WRT, WPA2-only enabled)

The backports modules fixed WPA2 personal for me (Wifi link 5100, jaunty), but I recently tried connecting to a WPA personal AP which failed. The new module in backports may still not fix WPA personal.

Same problem here, Wifi link 5100 won't connect with a WPA personal network or will crash seconds after connecting (very rare it is).

The card had to be forced into 802.11g to work without flaws. It worked when loading the iwlagn module with "iwlagn 11n_disable=1" and/or "11n_disable50=1" parameters using modprobe.

Besides, there are bits of solutions on this thread of intel site (http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1934). It's not exactly the same bug but it seems to be related somehow.

I hope this helps.

Me too:

Network Manger claims to connect to WPA2-secured network, but there is no actual connectivity. I can't ping even the wireless router.

Atheros AR5001X+ in a desktop computer.

Details of setup, logs, etc: http://ubuntuforums.org/showthread.php?t=1147423 and http://ubuntuforums.org/showthread.php?t=1144561

I haven't tried loading the back ports module, or rolling back the kernel, yet.

Follow up:
Still not working

 * Tried installing linux-backports-modules-jaunty-generic
 * Tried rolling back from kernel 2.6.27-11 to kernel 2.6.27-11.
 * Replaced Network Manager with WICD

I changed the summary and tags because, as the comments have shown, the problem is not specific to Intel hardware, or to Network Manager.

This has not been triaged. The upstreamed bug is about reconnect after a suspend. A number of commenters (myself include) still cannot connect *ever* to secured networks.

Also, none of the work-arounds are universal. At the moment user's like me are completely *stuck*.

Issue has not been upstreamed, and there is no established work-around. It has not been triaged.

Hello,

I'm the reporter of the bug, and I'd like update the information.

I installed linux-backports-modules-jaunty in Ubuntu and in Kubuntu.

Now I have other Fonera to test (2100 model) configured with WPA2 . After some test here the results:
 - I _always_ can connect to the LaFonera 2100 without any problem
 - I can connect to LaFonera 2200 _sometimes_ and only if It is the first connection when I turn on the computer. If I change to other wireless network and then I want to connect to the LaFonera I can't

A problem between the drivers and the chip of LaFonera 2200? Maybe, but I could connect without any problem in Intrepid.

Fonera 2100 and Fonera 2200 specs:

http://www.dd-wrt.com/wiki/index.php/La_Fonera_Hardware_Specifications

I was having similar problems in Ubuntu 9.04 Jaunty Jackalope on aToshiba satellite a75-s209 , ATI Radeon, gnome desktop . These have disappeared after I uninstalled compiz .

The issue seems to be with KDE Network Manager. Here is what I found out by running Ubunutu 9.04 and Kubuntu 9.04 live CDs:

- connection to non-secured wireless AP works in both
- connection to WPA secured AP works out of the box only from Ubuntu, but not from Kubuntu
- connection to WPA secured AP is possible to setup from Kubuntu through 'interfaces' and 'wpa_supplicant.conf' files as outlines in https://help.ubuntu.com/community/WifiDocs/WPAHowTo
- all of the above was done on the same wireless client (Lenovo R51 notebook) and AP (WRT54G with Tomtato firmware)

Some details:
--------------------
Ubuntu 9.04 Live off the CD
- Connects to WPA2 secured network out of the box
-- asks for WPA2 keyphrase
-- then asks for KeyRing (or smth like that) password, the step that is missing in KDE4 NetManager

Kubuntu 9.04 Live off the CD
- Does NOT connects to WPA2 secured network out of the box
- the workaround through wpa_supplicant.conf file does work

Some conclusions: since the 'low level' wireless setup (through wpa_supplicant) does work even in Kubuntu, it really seems to be the issue with the KDE Network Manager rather than chipset drivers....

Just my 2c..

It sounds very much like there are two bugs here. The first is the KDE network manager bug that volenin describes above that is fixed by installing linux-backports-modules-jaunty. The second seems to be hardware specific as described in Javier's last couple of messages.

I would like to add that I've the same problem with different hardware. I've a desktop pc (no brand) with an usb wireless network card (WN121T), working with the ndiswrapper module, on an Ubuntu 9.04 fresh installation. I can make a connection to a wpa access point, but after an random amount of time it disconnects and can't reconnect. This also happens with a WEP accespoint. If there is no encryption, the connection is stable.

On two installs of Jaunty Jacaklope Ubuntu:
One on a desktop PC, upgraded from a clean install of Ubuntu 8.10, a WPA2 secured network cannot be connected to, using a Netgear WPN111 USB wireless adaptor
One on a laptop using an Atheros AR5005G wireless adaptor, upgraded from a clean install of Xubuntu 8.10 to Jaunty, same problem.
Both try to connect, but never ask for any login credentials, and after a lengthy time, fail to connect at all.

i am not able to connect to a wpa2 peap mschapv2 network.

i am running jaunty 2.6.28-11 with an ar5212 pcmcia card. with wicd. i have tried wpa_supplicant with ndiswrapper, madwifi and ath5k drivers.

I am able to get and 'inet6' adress in ifconfig but when i run dhclient i can never get an IP adress : 'inet addr" in ifconfig.

I am also having a similar issue with Jaunty (2.6.28-11-generic) & Gnome (2.26.1) running on a Dell Mini 9 with a Broadcom wireless card. This was an initial Release Candidate install, but I have been performing regular updates.

I was able to connect to WPA2 Personal networks without any issues up until a week ago. Then it stopped working. I can successfully connect to unsecured networks. I have tried WPA Personal, WPA2 Personal and WPA/WPA2 Mixed. All are unsuccessful.

I have reinstalled WPASupplicant and Network Manager. I have uninstalled Network Manager and installed WICD. All of these attempts have been unsuccessful.

I am running a Linksys WRT54G with dd_WRT, hidden SSID, WPA/WPA2 Mixed.

Recently, I have noticed the Keyring popup message when I make changes to the wireless network settings. I don't remember these messages a couple weeks ago.

Could this have something to do with the WPA Passphrase getting stored in the keyring.

- Tim

I had the same problem but on the new Studio 15 ( 1550) using the 5100 wifi card.
Updating through the ubuntu packages from linuxwireless.org did not help. (Did not try loading the latest patches by compiling from source).
The problem was related to the n-mode, switching it off works as a work-around until the firmware gets updated:

create (or modify) iwlagn.conf:

sudo gedit /etc/modprobe.d/iwlagn.conf

and add:

options iwlagn 11n_disable=1
options iwlagn 11n_disable50=1

$ lspci | grep -i wireless
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

I've had this problem too. Installing linux-backports-modules-jaunty-generic and adding the "11n_disable*" options in iwlagn didn't fix it for me.

This is now fixed for me. I believe the remedy was installing the latest stable compat-wireless drivers: http://wireless.kernel.org/en/users/Download/stable/

I was able to attach to my WPA2 wireless router by broadcasting the SSID. If the SSID is hidden, it will not connect.

This was working when I was running the Jaunty RC (before the release). Then I ran the updater on the same machine to get the 9.04 release files and the wireless stopped auto connecting to my WPA2, hidden SSID router (WRT54G/dd-WRT). I have seen threads that point this issue to "wpa-supplicant".

Thanks,

Tim

I am still successfully connecting via WPA2 after enabling my SSID to be broadcast on my wireless router.

Can someone else verify their SSID broadcast options and test with SSID broadcast enabled. Then test with SSID broadcast disabled.

- Tim

thornbe:
With fully upgraded Jaunty, Network Manager cannot find the network with broadcast disabled, and still cannot connect successfully with it enabled for me. It asks for the network password a few times, then fails.

Fred,

Are you using "WPA & WPA2 Personal" as your "Security:" setting?

What is the brand of your wireless router?

How do you have the Security set on the wireless router?

Thanks,

Tim

Yes, it's WPA & WPA2 Personal
The router is a Netgear DG834PN, I'm not allowed to login to change any settings on it, but I know it's using the last patch from the Netgear website, and is also set to WPA2. It's not likely I could get him to change the security on it, so I'm stuck using it.

THORNBE Information:

Hardware: Dell Mini 9
Network Controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Network Driver: Broadcom STA Wireless Driver
Ubuntu: 9.04 (updated from 9.04 RC)
Kernel: 2.6.28-11-generic
Network Manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM Security Setting: WPA & WPA2 Personal
WPASupplicant Version: 0.6.6-2ubuntu1
Wireless Router: Linksys WRT54G
Router OS: dd-WRT
Wireless Security Settings: WPA & WPA2 Personal, TKIP/AES

Can others post their settings to see if we can find a correlation?

Thanks,

Tim

My info:

Hardware: Sony VAIO FZ430E laptop
Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
Network driver: Intel Wireless WiFi Link AGN driver for Linux (iwlagn 1.3.27ks)
OS: Kubuntu 9.04 x86_64 (fresh install)
Kernel: 2.6.28-13-generic
Network manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM security setting: WPA2-PSK
WPASupplicant version: 0.6.6-2ubuntu1
Wireless router: 2WIRE 3800HGV-B
Wireless security settings: WPA2-PSK, SSID broadcast enabled

Per my comment several weeks ago, I had trouble connecting at first, but things started working after I installed linux-backports-generic.

I also use this laptop on the wireless network at work, but that's an unsecured guest network and I've had no trouble with it.

Craig,

I see you have SSID Broadcast enabled. Can you disable the SSID broadcast and see if your VAIO can connect?

Thanks,

Tim

Linux Kernel Bug Tracker #12958 parted ways with this bug months ago.

I disabled my SSID broadcast last night and tested each of the WPA security settings on the wireless router. The WPA Personal, WPA2, WPA2 Mixed options with the SSID broadcast disabled did not allow my Dell Mini to connect at all. Once I enabled SSID broadcast, it would connect without issue. I did not change any settings on my netbook.

I have a co-worker that has a Dell Mini and runs 9.04, he just confirmed with the same issues. He has his wireless router set to broadcast the SSID.

Thanks,

Tim

Tim, per your request I tried disabling SSID broadcast at my main AP. My VAIO would then connect only to a wireless repeater further away (which does not seem to have an option to disable SSID broadcast), not to the main AP as it normally does.

Based on an above comment by "ryan" on 2009-04-01, it appears Kernel 2.6.28-9 was working and now kernels 2.6.28.10 and above are broken.

How would we proceed with identifying the kernel changes from version 2.6.28-9 to version 2.6.28-10 that would affect wireless networking, WPA security or interaction with Network Manager/WPA-Supplicant?

If the change is identified, how do we get it to be fixed?

Thanks,

Tim

The 2.6.28-14-generic kernel was released yesterday. I loaded the new kernel, disabled the SSID broadcast on my wireless router and I was able to auto connect through my wireless interface on my Dell Mini 9.

It appears this issue might have been fixed with this latest kernel. Can others that were having the same issue give the new kernel a try and report back their status?

Thanks,

Tim

thornbe: I'm not able to confirm that. a Dell Latitude c400 here with a clean Jaunty install updated to that kernel still cannot connect to any hidden wireless network, nor any secured network.
It seems to be regardless of the security used, at present, but as I have no way of changing my router's security, I can't verify that.

I can't connect too with NM using iwlagn with simple WPA authentication

My info:

Hardware: Keynux laptop
Network controller: Intel Corporation Wireless WiFi Link 5100
Network driver: iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
OS: Ubuntu 9.04 x86_64 (fresh install)
Kernel: 2.6.28-14-generic
Network manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM security setting: WPA-PSK
WPASupplicant version: 0.6.6-2ubuntu1
Wireless router: Acer
Wireless security settings: WPA-PSK, SSID broadcast enabled

linux-backport-modules-jaunty not installed but wireless-compat used instead in version 2.6

I joined syslog.txt

Thanks for your help

Should I upgrade NM ?

Same problem with WICD

Sorry iwlagn works for me now with WEP and simple WPA. I turned out bluetooth and it started working !?!
The problem seems to be else where. If someone has an idea, just let me know directly. I stop spoiling the list right now.
Best regards.

I found out one of the AP's was still configured to broadcast it's SSID. After disabling the SSID broadcast, I was not able to connect. The 2.6.28-14-generic kernel does not appear to fix the issue.

Sorry for the confusion.

Thanks,

Tim

Connecting manually with wpa_supplicant does not work when NetworkManager is running. Stopping NetworkManager enables wpa_supplicant to connect,

With NetworkManager running wpa_supplicant actually connects but is kicked of again. Any good hint on what to try on my systen to hunt this down?

With NetworkManager running but without having knetworkmanager running wpa_supplicant gives me this :

CTRL-EVENT-SCAN-RESULTS
WPS-AP-AVAILABLE
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
WPS-AP-AVAILABLE
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:09:5b:d0:37:ab
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS

After killing NetworkManager i get :

ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:09:5b:d0:37:ab
WPA: Key negotiation completed with 00:09:5b:d0:37:ab [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:09:5b:d0:37:ab completed (auth) [id=0 id_str=]

Problem is gone in

Linux phoenix 2.6.31-6-generic #25-Ubuntu SMP Fri Aug 14 16:28:28 UTC 2009 x86_64 GNU/Linux

We have two new notebooks and network manager keeps losing connection. When we check "edit connections"; the password has been changed to some garbled lengthy code. Something we didn't put in.

This happens all the time and its getting frustrating, especially with all the postings in launchpad and very few confirmed status listings.

The forums and web are plastered with this problem. There are over a hundred right here on this thread. I can't believe the foot dragging on this issue. Internet connections are a serious component of any computer. C'mon guys.

What the hell is up with network manager and why doesn't Canonical get with it?

I'd like to respond to Ronnie's recent comments...

Canonical has responded to this bug from the start. One of the problems is that multiple bugs have been intermingled in a single bug report and thus it makes it very hard to manage.

Javier, the *original* bug reporter stated that he couldn't connect to a WPA2/AES access point.

He also changed the original description to state that by installing linux-backports-generic, and the Jaunty version of network-manager from the PPA, that his problem resolved. Similarly, he's stated that it works in the current development release ( Karmic ) as well.

As for the garbled key / passphrase displayed when using "Edit Connections", unfortunately this is the way the network-manager applet used to store keys & passphrases. The keys/passphrases input by the user were transformed into the native format, which as you've pointed out makes it very hard to edit. This has been fixed in NM 0.8 which will be included in Ubuntu 9.10. For more details about hashed keys, you can read Dan William's blog which describes in detail how NM 0.7 handled keys ( search for "hashed keys" in the page ).

http://blogs.gnome.org/dcbw/category/networkmanager/

Also Ronnie, losing connections again is a *different* problem than what Javier originally described. If you're still experiencing this problem, please enter a *new* bug report. Please see the following Wiki page for more information on how to properly do so:

https://help.ubuntu.com/community/ReportingBugs

Finally, it's my opinion that the linux (ubuntu) portion of this bug should be marked WontFix, as installing backports modules seems to fix the original problem, and as pointed out above, it's fixed in Karmic.

The original issue was deemed to not be an issue with the plasma widget.

The linux package is fixed in Karmic.

I just reinstalled 9.04 on my Dell Mini 9. I installed all Updates. Tested wireless connectivity with the WPA Personal security and SSID Broadcast = Disabled. It would not connect. I installed the "generic-linux-backports" and anything related to wireless disappeared through Network Manager.

I tried to install Karmic and the installer "Ubiquity" kept crashing. So no Karmic Alpha 4, yet.

Does anyone have the exact steps to install the "backports" and the 0.8 version of Network Manager?

Thanks,

Tim

I was able to get the "generic-linux-backports" installed and working correctly with Network Manager. I disabled SSID Broadcasts on both of my wireless routers and my Dell Mini still can not connect automatically.

Any ideas?

Thanks,

Tim

I swapped out my Broadcom Corporation BCM4312 802.11b/g (rev 01) wireless adapter with an Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wireless adapter and I am able to connect to my wireless router with the SSID Broadcast "Disabled".

I am no longer using the "Broadcom STA Wireless Driver" and everything else has stayed the same. I am guessing the proprietary hardware drive was contributing to the problem.

Good luck to everyone,

Tim

Setting the linux Jaunty task to won't fix as it appears to be resolved via linux-backports-modules for Jaunty. Thanks.