From mboxrd@z Thu Jan  1 00:00:00 1970
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon, 25 Mar 2013 02:23:52 -0700
Subject: [ath9k-devel] ath9k not connecting to one particular network..
In-Reply-To: <CAKiAkGT7dJp_OHK7bySM4z9jEw6f=oBB5QHfP5Hc_4kE2utzzg@mail.gmail.com>
References: <CA+55aFworhoqD_7MQgtAkzcY5p_jJne0G9tvV54jojbpW-Z5Aw@mail.gmail.com>
	<CAKiAkGT7dJp_OHK7bySM4z9jEw6f=oBB5QHfP5Hc_4kE2utzzg@mail.gmail.com>
Message-ID: <CA+55aFw+SGHqFvbVpZmjGAfW_G5PikGyjFqszv-Q1RX5D7b08Q@mail.gmail.com>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

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?

                            Linus