From: "David H. Lynch Jr." <ml@dlasys.net>
To: linux-wireless@vger.kernel.org
Subject: Bandwidth monitoring
Date: Sun, 21 Oct 2012 15:58:18 -0400 [thread overview]
Message-ID: <1350849498.4859.27.camel@hp-dhlii> (raw)
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.
I am transmitting packets in monitor mode with specified frequencies and
parameters and i am trying to verify that I have sent what I intended
without getting a spectrum analyser.
thanks
next reply other threads:[~2012-10-21 19:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 19:58 David H. Lynch Jr. [this message]
2012-10-22 10:43 ` Bandwidth monitoring Christian Lamparter
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 0:44 David H. Lynch Jr.
2012-10-29 11:46 ` Christian Lamparter
2012-10-28 15:37 David H. Lynch Jr.
2012-10-28 20:59 ` Christian Lamparter
2012-10-23 18:58 David H. Lynch Jr.
2012-10-24 6:35 ` Christian Lamparter
2005-01-07 5:48 bandwidth monitoring Patrich Björklund
2005-01-06 20:28 Daniel Chemko
2005-01-06 19:04 Daniel Chemko
2005-01-06 19:39 ` Les Mikesell
2005-01-06 16:28 patrick.leduc
2005-01-06 17:09 ` J. Nerius
2005-01-06 17:42 ` Les Mikesell
2005-01-06 17:56 ` J. Nerius
2005-01-06 20:09 ` Michael Gale
2005-01-06 20:19 ` J. Nerius
2005-01-06 21:28 ` Michael Gale
2005-01-06 21:54 ` J. Nerius
2005-01-06 23:30 ` Michael Gale
[not found] ` <41DDA135.5000205@cisco.com>
2005-01-06 21:24 ` Michael Gale
2005-01-07 1:54 ` Mark E. Donaldson
2005-01-10 13:45 ` Fabiano Reis
2005-01-26 18:33 ` Ranjeet Shetye
2005-01-26 20:00 ` Jose Maria Lopez
[not found] <04a901c36e18$ad2d6650$2a0110ac@SAMHP>
2003-08-31 1:03 ` Bandwidth Monitoring Arnt Karlsen
2003-09-01 7:33 ` Ray Leach
2003-09-04 6:34 ` Dharmendra.T
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=1350849498.4859.27.camel@hp-dhlii \
--to=ml@dlasys.net \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.