From: Ben Greear <greearb@candelatech.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k, virtual stations, and WPA: No luck so far.
Date: Mon, 13 Sep 2010 16:18:09 -0700 [thread overview]
Message-ID: <4C8EB131.6090903@candelatech.com> (raw)
In-Reply-To: <201009140112.23751.chunkeey@googlemail.com>
On 09/13/2010 04:12 PM, Christian Lamparter wrote:
> On Tuesday 14 September 2010 00:38:14 Ben Greear wrote:
>> I'm having no luck getting WPA to work with two STA interfaces
>> on the same ath9k NIC.
>>
>> So far, I've done a bunch of hacking to only scan on the one
>> channel that we're currently using if 1+ stations are associated,
>> and some other logic to not call change-channel logic unnecessarily.
>>
>> Currently, I see wlan0 able to associate and authenticate with wpa_supplicant,
>> but sta1 (the other STA interface), won't work. A snippet from it's supplicant
>> log is below. No-encryption and WEP seems to work fine.
>> If anyone has any suggestions as to where I should look to debug this,
>> I'd welcome the pointers!
>
> First things first: Have you tried your "idea" with mac80211_hwsim?
No, I didn't know that existed..I will look for information
on that.
> Also, have you disabled the hardware crypto accelerator? Because if
> you spend one second to look at ath9k's set_key code, you "will see"
> why the hardware has a problem dealing with multiple keys for a
> single MAC (of your AP).
Yes, I think that part is correct:
[root@a230-ath9k ~]# cat /sys/module/ath9k/parameters/nohwcrypt
1
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-09-13 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 22:38 ath9k, virtual stations, and WPA: No luck so far Ben Greear
2010-09-13 23:12 ` Christian Lamparter
2010-09-13 23:18 ` Ben Greear [this message]
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=4C8EB131.6090903@candelatech.com \
--to=greearb@candelatech.com \
--cc=chunkeey@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).