cant connect to wifi N netowrks

Bug #653829 reported by Tim Lunn
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Maverick by Kirill Afonshin

Bug Description

Binary package hint: wpasupplicant

I am no longer able to connect to wifi N networks since updates in the last couple of days. Switching the router back into G mode and I can connect fine.

Running Maverick, installed about 1 week ago and completely up to date. Wifi was working fine up until about about 1-2 days ago.

below are the messages from the syslog.

Oct 3 09:11:48 arapiles2 kernel: [ 737.576991] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
Oct 3 09:11:48 arapiles2 kernel: [ 737.579377] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
Oct 3 09:11:48 arapiles2 kernel: [ 737.579386] wlan0:xx:xx:xx:xx:xx:xx denied association (code=18)
Oct 3 09:11:48 arapiles2 kernel: [ 737.579419] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
Oct 3 09:11:58 arapiles2 wpa_supplicant[1212]: Authentication with xx:xx:xx:xx:xx:xx timed out.
Oct 3 09:11:58 arapiles2 NetworkManager[1006]: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 3 09:11:58 arapiles2 NetworkManager[1006]: <info> (wlan0): supplicant connection state: disconnected -> scanning

Network controller: Intel Corporation PRO/Wireless 5100 AGN

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: wpasupplicant 0.6.10-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Sun Oct 3 09:16:28 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
SourcePackage: wpasupplicant

Revision history for this message
Tim Lunn (darkxst) wrote :
Revision history for this message
Tim Lunn (darkxst) wrote :

This is actually a kernel bug in linux-image-2.6.35-22-generic

Wifi N works fine, when I boot using older 2.6.32 kernel

affects: wpasupplicant (Ubuntu) → linux (Ubuntu)
Tim Lunn (darkxst)
description: updated
Revision history for this message
Rodrigo Delgado (rodrigo-delgado) wrote :

I am also affected, I am running Maverick

Oct 2 19:18:03 v3400 kernel: [ 1124.553141] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
Oct 2 19:18:03 v3400 kernel: [ 1124.555662] wlan0: authenticated
Oct 2 19:18:03 v3400 kernel: [ 1124.555704] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
Oct 2 19:18:03 v3400 kernel: [ 1124.571386] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x431 status=10 aid=257)
Oct 2 19:18:03 v3400 kernel: [ 1124.571393] wlan0: xx:xx:xx:xx:xx:xx denied association (code=10)
Oct 2 19:18:03 v3400 kernel: [ 1124.571417] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
Oct 2 19:18:13 v3400 wpa_supplicant[1376]: Authentication with xx:xx:xx:xx:xx:xx timed out.
Oct 2 19:18:13 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 2 19:18:13 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 2 19:18:16 v3400 wpa_supplicant[1376]: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='HomeNetwork' freq=2412 MHz)
Oct 2 19:18:16 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 2 19:18:16 v3400 kernel: [ 1137.573073] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
Oct 2 19:18:16 v3400 kernel: [ 1137.575784] wlan0: authenticated
Oct 2 19:18:16 v3400 kernel: [ 1137.575834] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
Oct 2 19:18:16 v3400 kernel: [ 1137.591483] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x431 status=10 aid=257)
Oct 2 19:18:16 v3400 kernel: [ 1137.591489] wlan0: xx:xx:xx:xx:xx:xx denied association (code=10)
Oct 2 19:18:16 v3400 kernel: [ 1137.591509] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
Oct 2 19:18:26 v3400 wpa_supplicant[1376]: Authentication with xx:xx:xx:xx:xx:xx timed out.
Oct 2 19:18:26 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 2 19:18:26 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 2 19:18:29 v3400 wpa_supplicant[1376]: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='HomeNetwork' freq=2412 MHz)
Oct 2 19:18:29 v3400 NetworkManager[1119]: <info> (wlan0): supplicant connection state: scanning -> associating

Network controller: Intel Corporation PRO/Wireless 5100 AGN

Uname: 2.6.35-22-generic-pae i686

Wireless was working OK until I had updated the distro.

Revision history for this message
Mikk Romulus (mikk-romulus-deactivatedaccount) wrote :

I have the same problem with intel 4965 chipset, it appeared within last couple of days. Really annoying, as i cant change the router to G mode and have to use a wired connection on my laptop now

Revision history for this message
Kirill Afonshin (pmvd) wrote :

I have the same problem with intel 4965 chipset, it appeared within last couple of days.
Everything works fine in 10.04. It looks like a regression.

Revision history for this message
Kirill Afonshin (pmvd) wrote :

The problem persists with wpasupplicant v0.7.3 from ppa.

Revision history for this message
Jordi R (jordi1983) wrote :

I'm also experiencing the same error.

I can use wifi G secured with WPA2 Personal, so I don't know if this has nothing to do with wpasupplicant, unless the algorithm to authenticate the N and the G networks for WPA2 Personal is different.

For me, updating wpasupplicant didn't work. I also updated the kernel version to 2.6.36rc7, no luck.

Now I'm using 2.6.36rc7 with wpasupplicant 0.7.2 and NetworkManager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2.

It is very impressive to see this kind of bugs at this late stage in the release cycle. For sure, the final release will have this bug, bothering a lot of users.

You developers think about it.

Revision history for this message
Tim Lunn (darkxst) wrote : Re: [Bug 653829] Re: cant connect to wifi N netowrks

looks like it has been disabled on purpose to fix another bug perhaps?

/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf

Some talk about things here suggest there is a intel firmware issue on
2.6.35 causing instability.
https://bugs.archlinux.org/task/20542

On 09/10/10 09:52, Jordi R wrote:
> I'm also experiencing the same error.
>
> I can use wifi G secured with WPA2 Personal, so I don't know if this has
> nothing to do with wpasupplicant, unless the algorithm to authenticate
> the N and the G networks for WPA2 Personal is different.
>
> For me, updating wpasupplicant didn't work. I also updated the kernel
> version to 2.6.36rc7, no luck.
>
> Now I'm using 2.6.36rc7 with wpasupplicant 0.7.2 and NetworkManager
> 0.8.1+git.20100810t184654.ab580f4-0ubuntu2.
>
> It is very impressive to see this kind of bugs at this late stage in the
> release cycle. For sure, the final release will have this bug, bothering
> a lot of users.
>
> You developers think about it.
>
>

Revision history for this message
Tim Lunn (darkxst) wrote :

just to confirm that after editing that file in my last post and set to
0. can connect to wifi N again.

Now lets see if its stable ;)

On 09/10/10 09:52, Jordi R wrote:
> I'm also experiencing the same error.
>
> I can use wifi G secured with WPA2 Personal, so I don't know if this has
> nothing to do with wpasupplicant, unless the algorithm to authenticate
> the N and the G networks for WPA2 Personal is different.
>
> For me, updating wpasupplicant didn't work. I also updated the kernel
> version to 2.6.36rc7, no luck.
>
> Now I'm using 2.6.36rc7 with wpasupplicant 0.7.2 and NetworkManager
> 0.8.1+git.20100810t184654.ab580f4-0ubuntu2.
>
> It is very impressive to see this kind of bugs at this late stage in the
> release cycle. For sure, the final release will have this bug, bothering
> a lot of users.
>
> You developers think about it.
>
>

Revision history for this message
Tim Lunn (darkxst) wrote :

Definitely appears to be some underlying issues with the current iwlagn drivers and/or firmware.

While I haven't had any drop-outs, performance is miserable at ~5mbps.

Revision history for this message
Rodrigo Delgado (rodrigo-delgado) wrote :

In my case, after editing intel-5300-iwlagn-disable11n.conf the system performs without problems and performance is OK. I have an Intel 5100 WLAN Card.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Tim,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Filiprino (filiprino) wrote :

Hello, I'm having this issue with an Atheros AR9285 card on a 1005PE netbook. My dmesg output:

[ 328.036772] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
[ 328.244226] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
[ 328.246682] wlan0: authenticated
[ 328.246758] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
[ 328.250511] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
[ 328.250530] wlan0: xx:xx:xx:xx:xx:xx denied association (code=18)
[ 328.250590] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 339.331095] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
[ 339.337099] wlan0: authenticated
[ 339.337183] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
[ 339.339881] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
[ 339.339901] wlan0: xx:xx:xx:xx:xx:xx denied association (code=18)
[ 339.346731] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 350.422330] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
[ 350.425249] wlan0: authenticated
[ 350.425331] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
[ 350.428861] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
[ 350.428881] wlan0: xx:xx:xx:xx:xx:xx denied association (code=18)
[ 350.435681] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 361.493508] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
[ 361.501101] wlan0: authenticated
[ 361.501186] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
[ 361.503820] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
[ 361.503840] wlan0: xx:xx:xx:xx:xx:xx denied association (code=18)
[ 361.503895] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)
[ 372.598971] wlan0: authenticate with xx:xx:xx:xx:xx:xx (try 1)
[ 372.605825] wlan0: authenticated
[ 372.617102] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1)
[ 372.639790] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=18 aid=0)
[ 372.639810] wlan0: xx:xx:xx:xx:xx:xx denied association (code=18)
[ 372.639869] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3)

It also happens with an Intel Wifi Link 4965abgn, both on Linux and Windows, so maybe the router's firmware is also based on Kernel Linux 2.6.35?

Revision history for this message
Filiprino (filiprino) wrote :

Hi,
I have updated to latest kernel (uname -a => Linux eeepc 2.6.36-020636-generic #201010210905 SMP Thu Oct 21 10:17:53 UTC 2010 i686 GNU/Linux) and it still can't connect to my wifi N network.

Revision history for this message
Tim Lunn (darkxst) wrote :

I tested with the lastest .35 mainline kernel and it seemed to be ok, a little slow, but definitely usable.

Now just switched back to the normal kernel and it still seems ok.

Getting around 70mbps, although used to get around 100mbps previously on Lucid.

tags: removed: needs-upstream-testing
Revision history for this message
Tim Lunn (darkxst) wrote :

Filiprino see comment #8 above.

Atleast for the intel wifi card, N has been disabled by default.

Revision history for this message
Filiprino (filiprino) wrote :

Hi Tim,

But it also happens with the Atheros on my netbook, and the Intel wifi card has the same issue on Windows (router denies association) :S

Revision history for this message
Filiprino (filiprino) wrote :

Hi all,
I finally could connect in Wireless N mode. I had to activate Wi-Fi Multimedia on the router, functionallity which is required for 802.11n.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Pieter (diepes) wrote :

Stardate 2012 ...

Changed my AP to N only.
Win7 laptop still connected but not my Ubuntu 12.4 Lenovo laptop with
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34)

After searching a bit i found this thread, and the note from Filiprino above sorted me out.
Had to switch "WMM(Wi-Fi Multimedia):" from off to auto. Leaving the ap on N only.

Suddenly ubuntu connected using WPA-PSK without any problems.
Even solved the problem for my Android ICS phone's wifi.

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.