From: Krishna Chaitanya <chaitanya.mgit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Cc: realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org
Subject: DMG Support
Date: Thu, 27 Jun 2019 22:45:54 +0530 [thread overview]
Message-ID: <CABPxzYLh=fcGFFAMxcNY9pFN8HOczgoPcYe_+NNMiW-uuRDe5Q@mail.gmail.com> (raw)
Hi Guys,
I am looking at support for DMG specific fields to radiotap, the only
discussion I have found didn't reach any conclusion [1].
Is there a plan to support these fields? It definitely needs a DMG
Type field with at least below params (from top of my head)
- MCS (and extended MCS) along with data rate mapping
- C-PHY
- SC-PHY
- Low power SC-PHY
-OFDM
- Beam/Sector/Antenna ID Information
- RCPI
[1] https://seclists.org/wireshark/2015/Aug/158
--
Thanks,
Regards,
Chaitanya T K.
next reply other threads:[~2019-06-27 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 17:15 Krishna Chaitanya [this message]
[not found] ` <CABPxzYLh=fcGFFAMxcNY9pFN8HOczgoPcYe_+NNMiW-uuRDe5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-27 18:14 ` DMG Support Richard Sharpe
[not found] ` <CACyXjPz5YD9VUcmbtO68nexEbjpaQOeZnLixs078c3FvW2B7eA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-27 19:56 ` Krishna Chaitanya
[not found] ` <CABPxzYJyabjkEx5SwF_iED8=vBcUxFj7WtHYG=n8ssAb6u5O_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-27 20:40 ` Richard Sharpe
[not found] ` <CACyXjPzNkK6Uq5kbA8O2e_4szD7T9r6DifkLCQ5ks1h1e4sAPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-28 8:02 ` Krishna Chaitanya
[not found] ` <CABPxzYKAc=J6x0UcC4TpSvgfuymyWS4N8bwCnA_dnDdS1rdgAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-28 8:24 ` Johannes Berg
[not found] ` <dfef0682ee1af5e92ccc6551f888b0118fcdd2f4.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2019-06-28 9:55 ` Krishna Chaitanya
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='CABPxzYLh=fcGFFAMxcNY9pFN8HOczgoPcYe_+NNMiW-uuRDe5Q@mail.gmail.com' \
--to=chaitanya.mgit-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org \
--cc=realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@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).