From: Richard Smith <smithbone@gmail.com>
To: Aaron Wood <woody77@gmail.com>,
Isaac Konikoff <konikofi@candelatech.com>
Cc: codel <codel@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] capturing packets and applying qdiscs
Date: Fri, 27 Mar 2015 14:13:08 -0400 [thread overview]
Message-ID: <55159DB4.10902@gmail.com> (raw)
In-Reply-To: <CALQXh-NGcC59w+8wqd=E3g+bXpyLvoyRzoLo40ez5R2aG-zHpA@mail.gmail.com>
On 03/27/2015 01:15 PM, Aaron Wood wrote:
> capturing in radiotap mode, you get RSSI/noise levels on the 802.11n
> packet, the rates involved, everything. It's very nice for digging into
> issues.
Nod. Done some of that.
> Unfortunately, the next problem is a "can't see the forest for the
> trees", as there are no good high-level analysis tools for captured
> traffic that I've found. Most of the commercial packages seem to offer
> summary stats, but not much more (nothing like airtime utilization over
> time, negotiated rates over time, aggregate/per-station throughput over
> time, etc.)
More nod and that's the sort of thing I'm specifically looking to find.
Out of all of these stations associated which station (or stations) is
chewing up the most RF time.
horst can show you some of this but its per packet and modulation and
not per station. I've been in contact with the author to see about
adding stats per station but he says it's a pretty big effort.
What I'm most likely going to do is use it's output feature to generate
a log and then post process that in python where I can easily aggregate
things on a per MAC address.
--
Richard A. Smith
next prev parent reply other threads:[~2015-03-27 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 21:39 [Cerowrt-devel] " Isaac Konikoff
2015-03-27 0:39 ` [Cerowrt-devel] [Bloat] " David Lang
2015-03-27 16:38 ` Isaac Konikoff
2015-03-27 17:15 ` Aaron Wood
2015-03-27 18:13 ` Richard Smith [this message]
2015-03-27 1:19 ` Dave Taht
2015-03-27 1:37 ` Dave Taht
2015-03-27 15:08 ` Richard Smith
2015-03-27 17:21 ` Aaron Wood
2015-03-27 18:13 ` Richard Smith
2015-03-27 19:00 ` Isaac Konikoff
2015-03-27 19:23 ` David Lang
2015-03-27 19:52 ` Richard Smith
2015-03-28 3:31 ` Dave Taht
2015-03-31 18:55 ` Isaac Konikoff
2015-04-01 15:13 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55159DB4.10902@gmail.com \
--to=smithbone@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=konikofi@candelatech.com \
--cc=woody77@gmail.com \
/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