radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: Re: [RFA v3] TLV fields for radiotap
Date: Tue, 09 Apr 2019 13:21:19 +0200	[thread overview]
Message-ID: <41a106db07ca04143ab20f668f0021a9d530ecd4.camel@sipsolutions.net> (raw)
In-Reply-To: <d1429268e48cd744bf4ed5fca04959821de2cda6.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Some code to back this up :-)

Here's a preliminary wireshark patch:
https://p.sipsolutions.net/0ad94ec27dbe26ad.txt

It works, but it's debatable if we really should add everything inside
the TLV. I guess we sort of should, but it makes looking for things a
bit tricky, so I guess at least we should resolve the name of the field
in the item_tree.

I should probably also rename item -> field here and in the proposed
spec text.

Here's a very rudimentary - and sort of wrong - patch for hwsim to
generate a sample capture file.

https://p.sipsolutions.net/83c6ff1e85e3e678.txt

It's wrong because it shouldn't put the channel field into a TLV, but
that's good for demonstrating what happens.

Finally, attached is a single packet capture from a test run over hwsim,
which can be used with wireshark.


Once this is adopted I'd try to get the wireshark base changes in, and
then really using it will only happen with future fields, e.g. S1G.

johannes

[-- Attachment #2: tlv-example.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 372 bytes --]

      parent reply	other threads:[~2019-04-09 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 11:15 [RFA v3] TLV fields for radiotap Johannes Berg
     [not found] ` <d1429268e48cd744bf4ed5fca04959821de2cda6.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2019-04-09 11:21   ` 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=41a106db07ca04143ab20f668f0021a9d530ecd4.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=radiotap-S783fYmB3Ccdnm+yROfE0A@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 NNTP newsgroup(s).