From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>
Subject: Question on how encryption keys are supposed to be handled.
Date: Mon, 17 Feb 2014 11:44:05 -0800 [thread overview]
Message-ID: <53026685.7040303@candelatech.com> (raw)
I've been debugging an issue where my ath10k firmware is running out of key
objects to allocate. This could be a simple issue in the firmware, but first I
wanted to try to figure out how things are supposed to work.
What I see in my firmware is that near time of association it allocates
4 keys. Two of them are multicast, and one of the multicast is index 0,
the second is index 1.
Then, some time later (probably on rekey), another multicast is added at index 2.
After that, key space is exhausted so I see errors in the kernel logs about adding
broadcast keys failing.
TCP and UDP traffic continues to flow, but I am not testing multicast traffic,
so maybe that would be failing.
So, question is: Is it expected that the mcast keys keep being added at increasing
key indexes? If so, what is the maximum index allowed?
Is this something primarily controlled at the supplicant level?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2014-02-17 19:44 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=53026685.7040303@candelatech.com \
--to=greearb@candelatech.com \
--cc=hostap@lists.shmoo.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).