From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Cc: "Luis R. Rodriguez" <mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: outgoing interface field
Date: Thu, 19 Jun 2008 21:28:48 +0200 [thread overview]
Message-ID: <1213903728.8967.92.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
For our particular implementation of AP mode with hostapd in Linux, we
are using radiotap-injection interfaces to send management frames.
Now, 802.11w (encrypted management frames) requires that those frames
are encrypted, due to key management issues we need to do that in the
kernel. This means we can no longer simply inject the frames, we need to
know, in the kernel, which interface to search for the key, since
multiple virtual AP interfaces/BSSes may be configured on a single PHY.
This requires that we have a radiotap field indicating the outgoing
interface to use for such key lookups. Further uses would be to use, for
data frames, the fragmentation/RTS threshold from the given interface.
I don't, off-hand, see any other OS requiring this, so I'm shopping
around asking vendors if I can have part of their vendor OUI namespace
(one of the sub-namespaces) for Linux, but if anybody sees value in such
a field for other OSes we can also add it to the standard.
Thoughts?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2008-06-19 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 19:28 Johannes Berg [this message]
[not found] ` <1213903728.8967.92.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 19:41 ` outgoing interface field Pavel Roskin
2008-06-19 19:44 ` Johannes Berg
[not found] ` <1213904654.8967.96.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 20:09 ` Pavel Roskin
2008-06-19 20:14 ` Johannes Berg
[not found] ` <1213906462.8967.110.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 20:29 ` Pavel Roskin
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=1213903728.8967.92.camel@johannes.berg \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.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.