All of lore.kernel.org
 help / color / mirror / Atom feed
From: Outback Dingo <outbackdingo@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k not connecting to one particular network..
Date: Mon, 25 Mar 2013 00:22:28 -0400	[thread overview]
Message-ID: <CAKYr3zwTaQ8GZnAmWLj3jzusyFNXnzypvxcNPkhUi660hsdY1w@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFworhoqD_7MQgtAkzcY5p_jJne0G9tvV54jojbpW-Z5Aw@mail.gmail.com>

bad firmware load on a crappy wireless AP probably, I just flashed the
latest firmware on a new Netgear, and had exactly the same issue
flashed back to the original firmware and the issue goes away, question is
whats the router and version? Ive seen it before also occasionally
using OpenWRT on some of my home units where a client would simply refuse
to connect, you could also ask the location your staying to reboot
the wireless AP, it might clear the error.


On Mon, Mar 25, 2013 at 12:06 AM, Linus Torvalds <
torvalds@linux-foundation.org> wrote:

> Ok, I'm sure this is something people have seen before, but it has me
> stumped.
>
> I'm on the road for a couple of days with my google ChromeBook pixel,
> which worked perfectly fine in the previous location I was at, and
> works fine at home. But in the current condo, the machine simply
> *cannot* connect to the wireless network here.
>
> The pixel has a :"Atheros AR9462 Rev:2" in it, and I know the network
> itself works, because my cellphone connects to it just fine.
>
> This is a WPA2-encrypted network, but so is my home network, and so
> was the one I connected to last week when traveling. I'm writing this
> on the Pixel, but I'm writing it connected to my phone doing a
> hotspot, because that works. Very odd.
>
> Working connection:
>
>   wlan0: authenticate with 02:1a:11:fc:8c:3b
>   wlan0: send auth to 02:1a:11:fc:8c:3b (try 1/3)
>   wlan0: authenticated
>   wlan0: associate with 02:1a:11:fc:8c:3b (try 1/3)
>   wlan0: RX AssocResp from 02:1a:11:fc:8c:3b (capab=0x411 status=0 aid=1)
>   wlan0: associated
>
> Non-working connection:
>
>   wlan0: authenticate with 50:46:5d:02:85:08
>   wlan0: send auth to 50:46:5d:02:85:08 (try 1/3)
>   wlan0: authenticated
>   wlan0: associate with 50:46:5d:02:85:08 (try 1/3)
>   wlan0: RX AssocResp from 50:46:5d:02:85:08 (capab=0x411 status=0 aid=10)
>   wlan0: associated
>
> .. now NM asks for the password again, and then I get:
>
>   wlan0: disassociating from 50:46:5d:02:85:08 by local choice (reason=3)
>
> I'm not seeing what the difference is. Except for that "aid=1" vs
> "aid=10", which I have no idea what it means.
>
> Looking in /var/log/messages, a successful connection looks like this:
>
>   Mar 24 20:48:42 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: associating -> associated
>   Mar 24 20:48:43 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: associated -> 4-way handshake
>   Mar 24 20:48:43 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: 4-way handshake -> completed
>
> while an unsuccessful one does this:
>
>   Mar 24 20:48:24 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: authenticating -> associated
>   Mar 24 20:48:24 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: associated -> 4-way handshake
>
> 10-second delay because it asks for password again, followed by:
>
>   Mar 24 20:48:34 pixel kernel: [ 2350.973914] wlan0: disassociating
> from 50:46:5d:02:85:08 by local choice (reason=3)
>   Mar 24 20:48:34 pixel kernel: [ 2350.980860] cfg80211: Calling CRDA
> to update world regulatory domain
>   Mar 24 20:48:34 pixel kernel: [ 2350.984796] wlan0: deauthenticating
> from 50:46:5d:02:85:08 by local choice (reason=3)
>   Mar 24 20:48:34 pixel NetworkManager[832]: <info> (wlan0):
> supplicant interface state: 4-way handshake -> disconnected
>
> Any idea? I tried loading the ath9k driver with debug=0xffff
> nohwcrypt=1, but that didn't really make any difference...
>
> Sure, the failing network has a different SSID and obviously a
> different password, but no, I didn't screw up typing in the password.
> What else can be different? Anything I can try? Relying on the really
> slow Edge connection from my cellphone gets me a working internet, but
> it's *slow*....
>
>                  Linus
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130325/3dbbe2ae/attachment.htm 

  reply	other threads:[~2013-03-25  4:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  4:06 [ath9k-devel] ath9k not connecting to one particular network Linus Torvalds
2013-03-25  4:22 ` Outback Dingo [this message]
2013-03-25  9:05   ` Linus Torvalds
2013-03-25  4:26 ` Joel Wirāmu Pauling
2013-03-25  9:23   ` Linus Torvalds
2013-03-25  9:38     ` Linus Torvalds
2013-03-25 10:12     ` Jouni Malinen
2013-03-25 10:38       ` Linus Torvalds
2013-03-25 11:06         ` Linus Torvalds
2013-03-25 11:30           ` Jouni Malinen
2013-03-25 12:17             ` Joel Wirāmu Pauling
2013-03-25 12:46               ` Jouni Malinen
2013-03-25 16:04             ` Linus Torvalds
2013-03-25 16:35               ` Jouni Malinen
2013-03-25 16:42                 ` Linus Torvalds
2013-03-25 18:03                   ` Peter Stuge
2013-03-25 19:01                     ` Adrian Chadd
2013-03-26  2:12                   ` Linus Torvalds
2013-03-26  9:58                     ` Jouni Malinen
2013-03-26 10:28                       ` Peter Stuge
2013-03-26 13:56                       ` Dan Williams
2013-03-26 15:25                       ` Linus Torvalds
2013-03-26 15:40                         ` Jouni Malinen
2013-03-26 19:20                           ` Luis R. Rodriguez
2013-03-26 19:20                             ` Luis R. Rodriguez
2013-03-25 10:43     ` Oleksij Rempel
2013-03-25  5:38 ` Adrian Chadd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKYr3zwTaQ8GZnAmWLj3jzusyFNXnzypvxcNPkhUi660hsdY1w@mail.gmail.com \
    --to=outbackdingo@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.