[ath9k-devel] ath9k not connecting to one particular network..

[Jouni Malinen <jouni@qca.qualcomm.com>]

On Mon, Mar 25, 2013 at 02:23:52AM -0700, Linus Torvalds wrote:
> Apparently this really is NetworkManager doing something wrong.
> 
> I'm running F18, so doing
> 
>         systemctl stop NetworkManager.service
>         ifconfig wlan0 up
>         iwlist scan
>         wpa_passphrase *essid* *password* > wpa_conf.txt
>         wpa_supplicant -i wlan0 -c wpa_conf.txt
> 
> and then
> 
>         dhclient wlan0
> 
> worked.

Did you happen to notice whether wpa_supplicant showed more than one
attempt at associating with the AP?

> Presumably NetworkManager should do the same, but doesn't. Or
> more likely, does something *more*, and that "something more" ends up
> confusing the driver and resetting.

It could be helpful to get wpa_supplicant debug output from both the
successful case (running it with manual configuration) and with NM
running it. I haven't done much debugging with NM, but this page seems
to show some guidance on how to collect the latter:
https://live.gnome.org/NetworkManager/Debugging
(for the former, just add -ddt on wpa_supplicant command line)

> Interestingly, the kernel messages from doing this were different:
> 
>   wlan0: RX AssocResp from 50:46:5d:02:85:08 (capab=0x411 status=0 aid=16)
> 
> notice how now it says "aid=16" instead of "aid=10". WTF?

That is likely irrelevant to the issue here. The AP usually allocates
the next available Association ID for the station and the exact value
depends on what other stations are currently associated. The only area
where this would have an effect during the association is in power
saving (buffered frames on the AP are indicated for a specific AID).

-- 
Jouni Malinen                                            PGP id EFC895FA