All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <jouni.malinen@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9kl multiple ssid AP
Date: Mon, 6 Apr 2009 20:37:03 +0300	[thread overview]
Message-ID: <1239039423.25377.4.camel@jm-desktop> (raw)
In-Reply-To: <49D9CCD8.7010607@hiramoto.org>

On Mon, 2009-04-06 at 02:35 -0700, Karl Hiramoto wrote:
> All of these cases seem to be working
> now.   What other cases is software encryption needed?

I do not have a full list, but most cases are in combinations of station
and AP mode interfaces being used at the same time. If you are only
using AP mode interfaces, the main case is use of multiple networks with
static WEP keys or maybe WEP in general in some combinations. I don't
think there has been very thorough testing on different multi-BSSID
combinations so far, so I cannot provide more detailed answer at this
point.

> Before setting nohwcrypt=1,  I was receiving the message in
> wireless-testing/drivers/net/wireless/ath9k/hw.c:2997:
> "received PCI FATAL interrupt\n");

Odd.. Hardware vs. software crypto should not really affect that, i.e.,
I would have just expected the default behavior to result in broken
connection (incorrect key used) and nohwcrypt=1 fixing that. Was this
with the two static WEP networks? When did this PCI FATAL message show
up (when starting hostapd? when trying to associate? when sending data
frames?)?

- Jouni

  reply	other threads:[~2009-04-06 17:37 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
2009-04-06 17:37               ` Jouni Malinen [this message]
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=1239039423.25377.4.camel@jm-desktop \
    --to=jouni.malinen@atheros.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.