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

[Oleksij Rempel <bug-track@fisher-privat.net>]

Am 25.03.2013 10:23, schrieb Linus Torvalds:
> On Sun, Mar 24, 2013 at 9:26 PM, Joel Wir?mu Pauling <joel@aenertia.net> wrote:
>> Can you try disabling network manager from the init scripts (I am not
>> sure which distro you are using as a base but
>> /etc/init.d/network-manager stop ) tends to work for a percentage of
>> machines.
>>
>> Then running wpa_supplicant manually.
>
> Bingo.
>
> 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. 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.
>
> 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?
>
> So now I have working internet, can anybody suggest something for the
> NM bug-report? Some way for the NM people to guess at what they do
> wrong? Any ideas of why it would happen only for this particular
> network?
>

For some months there was a bug in NetworkManager or dhcp client it 
used. If dhcp leas time is unlimited then it fails to connect. By 
changing default dhcpclient for NEtworkManager it was possible to work 
around it. MAy bit it is that issue.


-- 
Regards,
Oleksij