From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 11D7F21F3F0; Fri, 27 Mar 2015 10:21:32 -0700 (PDT) Received: by qcay5 with SMTP id y5so22272543qca.1; Fri, 27 Mar 2015 10:21:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kT2XrT5DsNU8MmtckzJDAyTVmfaOswY+cTRwA3pQ7WU=; b=SujdKT0gxLJfmggWnuY2mJYr6A0aX47DiF5fnA/r5GrvL1hoEITNJbFnSjPch8AgfH C4bhHpvzMtuJvAbW59lipdiwjkryzsjPqnv+yrbx+9iisEwOVCGs9f9cCrgf6RY3WBik mNxjmuRf2QCSctymjSobofOQM0smWGqFRxVQhwqLUXI4Jrko7iI48XauGJV3PpIMIO3Z 0EhbcD/zmw96xO198ymqvXZavDuEMfs/mUb89VM240W18in25e17ay6x+aXrEWLPT2td u2l/0hEFOp5x8jO9zuvQO9PZl+iJnHaBh2E+Ff0AUiURQE0nKVNDRcHO4+gFJn0szHS1 WfNA== MIME-Version: 1.0 X-Received: by 10.55.21.140 with SMTP id 12mr41582235qkv.95.1427476891691; Fri, 27 Mar 2015 10:21:31 -0700 (PDT) Received: by 10.96.175.65 with HTTP; Fri, 27 Mar 2015 10:21:31 -0700 (PDT) In-Reply-To: <55157250.6030208@gmail.com> References: <55147C8A.4030804@candelatech.com> <55157250.6030208@gmail.com> Date: Fri, 27 Mar 2015 10:21:31 -0700 Message-ID: From: Aaron Wood To: Richard Smith Content-Type: multipart/alternative; boundary=001a11473a7c0df22d0512485d01 Cc: bloat , codel , cerowrt-devel Subject: Re: [Cerowrt-devel] [Bloat] capturing packets and applying qdiscs X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2015 17:22:01 -0000 --001a11473a7c0df22d0512485d01 Content-Type: text/plain; charset=UTF-8 On Fri, Mar 27, 2015 at 8:08 AM, Richard Smith 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 --001a11473a7c0df22d0512485d01 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Mar 27, 2015 at 8:08 AM, Richard Smith <smithbone@gmail.com<= /a>> wrote:
Using horst I'v= e discovered that the major reason our WiFi network sucks is because 90% of= the packets are sent at the 6mbit rate.=C2=A0 Most of the rest show up in = the 12 and 24mbit zone with a tiny fraction of them using the higher MCS ra= tes.

Trying to couple the radiotap info with the packet decryption to discover t= he sources of those low-bit rate packets is where I've been running int= o difficulty.=C2=A0 I can see the what but I haven't had much luck on t= he why.

I totally agree with you that tools other than wireshark for analyzing this= seem to be non-existent.

Using the followi= ng filter in Wireshark should get you all that 6Mbps traffic: =C2=A0
<= div>
radiotap.datarate =3D=3D 6

Then= it's pretty easy to dig into what those are (by wifi frame-type, at le= ast).=C2=A0 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 br= oadcast rate.

without capturing the WPA exchange, = the contents of the data frames can't be seen, of course.
-Aaron
--001a11473a7c0df22d0512485d01--