From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.candelatech.com (mail2.candelatech.com [208.74.158.173]) by huchra.bufferbloat.net (Postfix) with ESMTP id D09B221F417; Fri, 27 Mar 2015 12:00:53 -0700 (PDT) Received: from [192.168.100.65] (unknown [50.251.239.81]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.candelatech.com (Postfix) with ESMTPSA id 1876840EA6B; Fri, 27 Mar 2015 12:00:53 -0700 (PDT) Message-ID: <5515A8DF.8050902@candelatech.com> Date: Fri, 27 Mar 2015 12:00:47 -0700 From: Isaac Konikoff User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Aaron Wood , Richard Smith References: <55147C8A.4030804@candelatech.com> <55157250.6030208@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------040505080103070108050501" Cc: codel , cerowrt-devel , bloat Subject: Re: [Codel] [Cerowrt-devel] [Bloat] capturing packets and applying qdiscs X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2015 19:01:23 -0000 This is a multi-part message in MIME format. --------------040505080103070108050501 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Thanks for pointing out horst. I've been trying wireshark io graphs such as: retry comparison: wlan.fc.retry==0 (line) to wlan.fc.retry==1 (impulse) beacon delays: wlan.fc.type_subtype==0x08 AVG frame.time_delta_displayed I've uploaded my pcap files, netperf-wrapper results and lanforge script reports which have some aggregate graphs below all of the pie charts. The pcap files with 64sta in the name correspond to the script reports. candelatech.com/downloads/wifi-reports/trial1 I'll upload more once I try the qdisc suggestions and I'll generate comparison plots. Isaac On 03/27/2015 10:21 AM, Aaron Wood wrote: > > > 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 --------------040505080103070108050501 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Thanks for pointing out horst.

I've been trying wireshark io graphs such as:
retry comparison:  wlan.fc.retry==0 (line) to wlan.fc.retry==1 (impulse)
beacon delays:  wlan.fc.type_subtype==0x08 AVG frame.time_delta_displayed

I've uploaded my pcap files, netperf-wrapper results and lanforge script reports which have some aggregate graphs below all of the pie charts. The pcap files with 64sta in the name correspond to the script reports.

candelatech.com/downloads/wifi-reports/trial1

I'll upload more once I try the qdisc suggestions and I'll generate comparison plots.

Isaac

On 03/27/2015 10:21 AM, Aaron Wood wrote:


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


--------------040505080103070108050501--