All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k not connecting to one particular network..
Date: Tue, 26 Mar 2013 08:25:20 -0700	[thread overview]
Message-ID: <CA+55aFw7OO1KtW38Ph0Ru__Q8K-tDVN3tL=8g-hn_1fGUnxoqg@mail.gmail.com> (raw)
In-Reply-To: <20130326095829.GA5612@jouni.qca.qualcomm.com>

On Tue, Mar 26, 2013 at 2:58 AM, Jouni Malinen <jouni@qca.qualcomm.com> wrote:
>
> If you still happen to be at the location with this AP, it could be
> useful to confirm that this kernel interface difference is indeed the
> reason by running the manual configuration case with -Dnl80211 added to
> the wpa_supplicant command line to force nl80211 interface to be used.

Ok, added to the bugzilla. I'm still in the condo, but I'm leaving
soon and need to pack up, so this is likely the last thing I can do..

It is indeed the nl80211 part that causes problems, so I guess we're
back to an actual ath9k issue.

> In addition, you could try to collect the frames exchanged by the
> success and failure cases using a monitor interface:
>
> iw wlan0 interface add mon0 type monitor
> ifconfig mon0 up
> dumpcap -i mon0 -w /tmp/capture.pkt
>
> And then run the success/failure case.

Ok, will try to do that too.

                Linus

  parent reply	other threads:[~2013-03-26 15:25 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
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 [this message]
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='CA+55aFw7OO1KtW38Ph0Ru__Q8K-tDVN3tL=8g-hn_1fGUnxoqg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --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.