Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Richard Smith <smithbone@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	codel <codel@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] capturing packets and applying qdiscs
Date: Fri, 27 Mar 2015 10:21:31 -0700	[thread overview]
Message-ID: <CALQXh-M-G3C9XyFw3aJ=UmSPnwO76Gc88v8L9K=T2=jYr_9jyA@mail.gmail.com> (raw)
In-Reply-To: <55157250.6030208@gmail.com>

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

On Fri, Mar 27, 2015 at 8:08 AM, Richard Smith <smithbone@gmail.com> wrote:

> Using horst I've discovered that the major reason our WiFi network sucks
> is because 90% of the packets are sent at the 6mbit rate.  Most of the rest
> show up in the 12 and 24mbit zone with a tiny fraction of them using the
> higher MCS rates.
>
> Trying to couple the radiotap info with the packet decryption to discover
> the sources of those low-bit rate packets is where I've been running into
> difficulty.  I can see the what but I haven't had much luck on the why.
>
> I totally agree with you that tools other than wireshark for analyzing
> this seem to be non-existent.


Using the following filter in Wireshark should get you all that 6Mbps
traffic:

radiotap.datarate == 6

Then it's pretty easy to dig into what those are (by wifi frame-type, at
least).  At my network, that's mostly broadcast traffic (AP beacons and
whatnot), as the corporate wifi has been set to use that rate as the
broadcast rate.

without capturing the WPA exchange, the contents of the data frames can't
be seen, of course.

-Aaron

[-- Attachment #2: Type: text/html, Size: 1543 bytes --]

  reply	other threads:[~2015-03-27 17:21 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
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 [this message]
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='CALQXh-M-G3C9XyFw3aJ=UmSPnwO76Gc88v8L9K=T2=jYr_9jyA@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=smithbone@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