From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Question on keycache size.
Date: Wed, 11 Jan 2012 13:55:03 -0800 [thread overview]
Message-ID: <4F0E0537.2000509@candelatech.com> (raw)
I have an ath9k AP, running 3.0.8 kernel (with a few tweaks).
nohwcrypt is enabled.
I set up some other machines with virtual stations, a total of
around 450 and had them associate with the AP.
It seems to have worked, at least for a while, but then I started
seeing loss of station communication, and in the AP logs I see
things like this:
Jan 11 13:47:03 localhost kernel: ath: keycache entry 228 out of range
It appears the keycache max is always 128. Any idea what this
message really means? Is there a hard upper limit of 128 stations
for ath9k NICs?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2012-01-11 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 21:55 Ben Greear [this message]
2012-01-12 8:27 ` [ath9k-devel] Question on keycache size Mohammed Shafi
2012-01-12 16:02 ` Ben Greear
2012-01-12 19:46 ` Adrian Chadd
2012-01-12 20:14 ` Ben Greear
2012-01-12 20:34 ` Ben Greear
2012-01-12 23:11 ` Ben Greear
2012-01-12 23:53 ` Adrian Chadd
2012-01-12 23:59 ` Ben Greear
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=4F0E0537.2000509@candelatech.com \
--to=greearb@candelatech.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.