From: Johannes Berg <johannes@sipsolutions.net>
To: Guy Harris <gharris@sonic.net>
Cc: "radiotap@radiotap.org" <radiotap@radiotap.org>
Subject: Re: Copy-and-paste error on the page for the "antenna noise" field?
Date: Thu, 19 Jan 2023 20:17:41 +0100 [thread overview]
Message-ID: <632d65809d73ab9ce2b0e22f9857230fd5a296df.camel@sipsolutions.net> (raw)
In-Reply-To: <965F651B-6310-4B52-B12B-6F54785C1525@sonic.net>
On Thu, 2023-01-12 at 00:58 -0800, Guy Harris wrote:
> On Jan 12, 2023, at 12:30 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> > I don't know what adapter they're using to capture, but it _looks_ like
> > mac80211 (with the per-antenna signal encoded that way),
>
> Should that encoding scheme be documented, so as to encourage its use
> in other OS's 802.11 frameworks?
I don't know.
For the record, the encoding is to use a separate radiotap namespace for
each antenna, and then put an antenna signal and antenna field into it,
with the signal value and antenna number, respectively.
It's honestly not the greatest encoding, but it's sometimes useful to
have that data.
I've been hoping to replace namespaces with TLVs, but obviously in this
case that doesn't work since the namespace holds the two pieces of
information together ...
johannes
prev parent reply other threads:[~2023-01-19 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 3:16 Copy-and-paste error on the page for the "antenna noise" field? Guy Harris
2023-01-12 7:46 ` Johannes Berg
2023-01-12 8:15 ` Guy Harris
2023-01-12 8:30 ` Johannes Berg
2023-01-12 8:58 ` Guy Harris
2023-01-19 19:17 ` Johannes Berg [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=632d65809d73ab9ce2b0e22f9857230fd5a296df.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gharris@sonic.net \
--cc=radiotap@radiotap.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).