From: Karl Hiramoto <karl@hiramoto.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9kl multiple ssid AP
Date: Mon, 06 Apr 2009 11:35:20 +0200 [thread overview]
Message-ID: <49D9CCD8.7010607@hiramoto.org> (raw)
In-Reply-To: <1238783295.7153.12.camel@jm-desktop>
Jouni Malinen wrote:
> On Fri, 2009-04-03 at 04:37 -0700, Karl Hiramoto wrote:
>
>
>> Another case. two WEP APs essid 1 works but essid2 does not (no
>> traffic flow). an iwlist <dev> wlan0 on another machine shows the two
>> AP's with WEP. Windows shows the WEP APs.
>>
>
> Static WEP keys were not configured for secondary BSSes. This is now
> fixed in hostap.git.
>
> Please also note that this is likely a combination that ath9k does not
> currently handle automatically, so you may have to use software crypto
> (nohwcrypt=1 module parameter) as a workaround for the time being. This
> will eventually be handled automatically, so that the driver can revert
> to software encryption/decryption when needed.
>
> - Jouni
>
>
>
Thanks for all the fixes Journi, All of these cases seem to be working
now. What other cases is software encryption needed?
Before setting nohwcrypt=1, I was receiving the message in
wireless-testing/drivers/net/wireless/ath9k/hw.c:2997:
"received PCI FATAL interrupt\n");
--
Karl
next prev parent reply other threads:[~2009-04-06 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 17:46 [ath9k-devel] ath9kl multiple ssid AP Karl Hiramoto
2009-04-01 18:30 ` Jouni Malinen
2009-04-02 14:34 ` Karl Hiramoto
2009-04-02 16:57 ` Jouni Malinen
2009-04-03 8:44 ` Karl Hiramoto
2009-04-03 11:37 ` Karl Hiramoto
2009-04-03 18:28 ` Jouni Malinen
2009-04-06 9:35 ` Karl Hiramoto [this message]
2009-04-06 17:37 ` Jouni Malinen
2009-04-03 18:24 ` Jouni Malinen
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=49D9CCD8.7010607@hiramoto.org \
--to=karl@hiramoto.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.