Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Smith <smithbone@gmail.com>
To: Aaron Wood <woody77@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 14:13:17 -0400	[thread overview]
Message-ID: <55159DBD.3060702@gmail.com> (raw)
In-Reply-To: <CALQXh-M-G3C9XyFw3aJ=UmSPnwO76Gc88v8L9K=T2=jYr_9jyA@mail.gmail.com>

On 03/27/2015 01:21 PM, Aaron Wood wrote:

> Using the following filter in Wireshark should get you all that 6Mbps
> traffic:
>
> radiotap.datarate == 6

Thanks.  I'd not discovered that yet although I have so much of it that 
finding 6mbit packets is not much of a problem.

> 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.

Yeah. Beacons are supposed to be that low but that's only every 100ms.
On my network its there are loads of data packets that are sent at 6mbit.

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

And this is where I seem to stall out.  Even when I capture the full WPA 
exchange I only have limited success at getting wireshark to decode all 
my traffic.

I have more success with using airdecap-ng decoding and then feeding 
that to wireshark but there are still times when it can't decode things 
and I can't see why.  The full WPA exchange is clearly visible in the 
packet capture.

-- 
Richard A. Smith

  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
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 [this message]
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=55159DBD.3060702@gmail.com \
    --to=smithbone@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --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