From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org,
"Luis R. Rodriguez"
<mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: outgoing interface field
Date: Thu, 19 Jun 2008 16:29:11 -0400 [thread overview]
Message-ID: <1213907351.3240.54.camel@dv> (raw)
In-Reply-To: <1213906462.8967.110.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
On Thu, 2008-06-19 at 22:14 +0200, Johannes Berg wrote:
> > Besides, radiotap headers are designed to be transferable between
> > systems. It should be possible to send frames with radiotap headers
> > from another system, possibly with a different endianness and
> > different
> > wireless hardware. Encoding local data (VAP number) makes radiotap
> > headers system-specific.
>
> This isn't designed to be ever saved to disk, it's for communication
> between userspace and the kernel when running an AP. We just happen to
> use radiotap for that to save inventing yet another interface.
Then there is very little point in discussing it. I thought you were
going to suggest some elegant addition to the standard. Piggybacking
the frames with some OS and system specific data is not.
> > It's funny, we are creating the rules that exclude us, and then we are
> > shopping around for sponsors. We need exceptions for experimental use.
>
> Actually, I just figured out that the OUIs have a 'locally assigned' bit
> like MAC addresses (well I guess MAC addresses inherit it from OUIs), so
> we can use that and assign "experimental" OUIs to ourselves as long as
> they don't clash within radiotap.
OK, fine.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-06-19 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 19:28 outgoing interface field Johannes Berg
[not found] ` <1213903728.8967.92.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 19:41 ` 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 [this message]
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=1213907351.3240.54.camel@dv \
--to=proski-mxxj517/zsq@public.gmane.org \
--cc=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 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 read-only IMAP folder(s) and NNTP newsgroup(s).