From: Christian Lamparter <chunkeey@googlemail.com>
To: "David H. Lynch Jr." <ml@dlasys.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bandwidth monitoring
Date: Mon, 22 Oct 2012 12:43:01 +0200 [thread overview]
Message-ID: <201210221243.02059.chunkeey@googlemail.com> (raw)
In-Reply-To: <1350849498.4859.27.camel@hp-dhlii>
On Sunday, October 21, 2012 09:58:18 PM David H. Lynch Jr. wrote:
> I am looking for an easy means to determine the characteristics of a
> transmitted packet.
> Particularly whether it is HT20/HT40-/HT40+ I have used a variety of
> sniffers, airodump, wireshark, ... and I can not seem to find anything
> that will tell me what I am after - or I do not know how to use them.
differentiating between HT40+ and HT40- will be difficult to do with
just one standard wifi device (should be possible with two though).
If you use mac80211, have you setup your monitor channel by adding
the HT20/HT40+/HT40- flag?
# iw dev wlanX set channel 1 HT40+ (or HT40-/HT20)
This might help.
As for retrieving the information:
If a HT20/HT40 frame was received, it should have a radiotap
IEEE80211_RADIOTAP_MCS header element (on the monitor interface dump).
In this element should provide the MCS and flags for
- BW40 (if false => HT20, if true => HT40+ or HT40- depending
on the channel configuration)
- Short GI
- Greenfield flag
- (LDPC)
But I don't know if any of this information is parsed by any of the
current tools (depends on the version I guess). At least for wireshark
you can always look at the raw hex dump of the package, so it should
be there! The definitions of what RADIOTAP_MCS bit means what are in:
<include/net/ieee80211_radiotap.h>
Regards,
Chr
next prev parent reply other threads:[~2012-10-22 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 19:58 Bandwidth monitoring David H. Lynch Jr.
2012-10-22 10:43 ` Christian Lamparter [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 18:58 David H. Lynch Jr.
2012-10-24 6:35 ` Christian Lamparter
2012-10-28 15:37 David H. Lynch Jr.
2012-10-28 20:59 ` Christian Lamparter
2012-10-29 0:44 David H. Lynch Jr.
2012-10-29 11:46 ` Christian Lamparter
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=201210221243.02059.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ml@dlasys.net \
/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).