From: Ignacy Gawedzki <i@lri.fr>
To: linux-wireless@vger.kernel.org
Subject: ath9k_htc: station unable to authenticate
Date: Tue, 18 Jun 2013 18:48:12 +0200 [thread overview]
Message-ID: <20130618164812.GA32498@zenon.in.qult.net> (raw)
Hi,
After a lot of git-bisecting and other testing, it appears that commit
382a103b2b528a3085cde4ac56fc69d92a828b72 is the culprit.
To reproduce the problem, use backports-20130607, and the ath9k defconfig
(with no change otherwise).
The station is unable to authenticate with WPA2 to the AP. Interestingly
enough, if a monitor vif is created and upped beforehand, the authentication
succeeds.
After reverting the commit, authentication succeeds very quickly (without the
need to up a monitor vif), just as expected.
Note that I have kernel 3.8.0 (as per Ubuntu 13.04) and that original
ath9k_htc driver works as expected. This has been also tested on Debian with
driver from original kernel 3.9 (i.e. without backports).
For the moment I can live with the commit reverted, but I suppose it's been
there to fix something else, so this should probably be looked into by someone
more knowledgeable than me.
Ignacy
--
A person is shit's way of making more shit.
-- S. Barnett, anthropologist.
reply other threads:[~2013-06-18 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130618164812.GA32498@zenon.in.qult.net \
--to=i@lri.fr \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox