From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F07273B29E for ; Wed, 10 Oct 2018 13:21:15 -0400 (EDT) Received: by mail-qt1-x831.google.com with SMTP id v19-v6so6581696qtg.2 for ; Wed, 10 Oct 2018 10:21:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=/B6CBud8lzx7+lEX/0jVM/SOQ4cqz1J0GDr+wQSIxWs=; b=kjiAlTw4V8/mkbAiWcOpgujMC/V7g3tIyXNMowECPld3a9cTnZjaf47DuW3OvEP1/a N9v/It6IskVIz+RyuFY5/xSh5TyRqTm1j6jfPZBzizKScD9imkOAgT062S3W/OA5LSdw trEENEDXLFfpcq6mvkwkJzynAhkRwKO7XLTl0Af3kDYyEtoK0iuUseOAm9A8HE1auvFR fjSL1YMvnSiy1j4mv3EnCFse2ESyuWEpJdip7wKa8tTdKRGRKDgcLYcs7E6apdTdhK8K BQ+uPYmMRWt1O2EuFi7jgIYyHOHdGIHvYAcHZ8ao99/Sj3wRfc19a8kl+7hb4UfHXtZi 4ZSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=/B6CBud8lzx7+lEX/0jVM/SOQ4cqz1J0GDr+wQSIxWs=; b=uC03MaR5NL0SirBqVakjTu9zRITvQF6ggscgYZbDlUTxPy+DlZD+XpS7sbiHXP6oDT LmaoFnGwkmHTiwT569rAMGVMZxzX1I6th9+8b6mJ4ZpY6/xaCjU1+VuCJMfvXyaMVBRI BF6P79j9SV8gi78t82rT9sUS/lgvuHVE+//xnNhlilhBGESWVylc/yCxG3ydjU8kipm9 o7KgQbkZSp9vl5gWS+swUpIA5Yk1Q4ugfnn/6ek0dDB6LiR2F8RcFOeemyPO4/OA1ivs pNt0MdSiIKKAdwqW8k6p1LnQaCUJr5I1Si65mpsbLI4s47CqD5tw26RaKPTpaA4xnam6 A/Zw== X-Gm-Message-State: ABuFfogVQxsYZ8Lar3IunW6XmD0S7+BVN29wcLM2pKkruawRFYNR1lYg xRw2n34QQaYtG5cvpUhORgjk4OIaMliRoTs9bN7U6A== X-Google-Smtp-Source: ACcGV61/+3W8b2iMozuFPLnT0lTNZZvrM+88kTfaN8xLe2w8tKVGDT32GWGhqju3R15bffij7LNpIFpc5DCaZ1BgPVA= X-Received: by 2002:a0c:9609:: with SMTP id 9mr8011117qvx.129.1539192074808; Wed, 10 Oct 2018 10:21:14 -0700 (PDT) MIME-Version: 1.0 References: <87pnwqaiso.fsf@toke.dk> <01b77936-f6d4-271a-d7d2-0fd2cf70f7bd@candelatech.com> In-Reply-To: <01b77936-f6d4-271a-d7d2-0fd2cf70f7bd@candelatech.com> From: Dave Taht Date: Wed, 10 Oct 2018 10:21:01 -0700 Message-ID: To: Make-Wifi-fast Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Make-wifi-fast] Fwd: Tool to debug wifi pkt sniffs? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 17:21:16 -0000 ---------- Forwarded message --------- From: Ben Greear Date: Wed, Oct 10, 2018 at 10:10 AM Subject: Re: Tool to debug wifi pkt sniffs? To: Dave Taht , Toke H=C3=B8iland-J=C3=B8rgensen Cc: linux-wireless On 10/03/2018 01:29 PM, Dave Taht wrote: > On Wed, Oct 3, 2018 at 1:16 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> >> Ben Greear writes: >> >>> Hello, >>> >>> I often find myself wanting to figure out what equipment is to blame (a= nd why) >>> in a wifi environment. >>> >>> I am thinking writing a tool that would parse a pcap file and look at f= rames >>> in enough detail to flag block-ack bugs, rate-ctrl bugs, guess at the s= niffer's >>> capture ability, etc. >>> >>> Does anyone have anything already written that they would like to share= , or know >>> of projects that might already do some of this? >> >> Not sure if this fits your criteria, but Sven's tool to create airtime >> charts from packet sniffing data immediately came to mind: >> >> https://github.com/cloudtrax/airtime-pie-chart > > I have used that. Oy, it's a PITA. Some of kathie's code over here > (example: https://github.com/pollere/pping ) uses the slightly less > painful http://libtins.github.io/ library for parsing packets. I couldn't find anything that did what I wanted, so I wrote my own. The (perl) code is in the wifi-diag directory of this public repo: https://github.com/greearb/lanforge-scripts The rest of the scripts in that repo are not related to the wifi-diag script, so just ignore those. Here is example output for what I have so far: https://www.candelatech.com/oss/wifi-diag/netgear-up-5s/index.html The general idea is to get a performance test going, and then use tshark or similar to grab a short sample (my script is slow, it can process only about 400 packets per second on my desktop, so a 5 sec capture at full speed takes around 5 minutes to process), and then pipe that decoded pcap into my script. It tries to pay attention to latencies between block-ack and next AMPDU fra= me, MCS distributions, packet-type distributions, retries, and other such things. I'm guessing tweaking wmm settings (or changing QoS in the generated traffic) would be visible in this kind of metric, for instance. The goal is to be able to answer the question of why one AP is faster or slower than another when running the same test case. Feedback (and even patches) is welcome...what other things can I report that would be helpful? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --=20 Dave T=C3=A4ht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740