From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from masada.superduper.net (masada.superduper.net [85.119.82.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 944893B2A4 for ; Wed, 29 Apr 2020 13:09:03 -0400 (EDT) Received: from [52.119.118.138] (helo=[192.168.130.24]) by masada.superduper.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1jTqCc-0004IM-Mz; Wed, 29 Apr 2020 18:08:56 +0100 From: Simon Barber Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_D51844DF-06E7-459D-B534-9B530270E3EB" Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Date: Wed, 29 Apr 2020 10:08:50 -0700 In-Reply-To: <728D55C2-2B57-4C4E-9497-A1461FD3AB3F@timhiggins.com> Cc: Make-Wifi-fast , Avery Pennarun To: Tim Higgins References: <3f371367-4535-d29a-4cf2-abca8adb9542@timhiggins.com> <171c2108dc8.27a9.e972a4f4d859b00521b2b659602cb2f9@superduper.net> <8283CA5F-D406-47D5-96B3-0F7D21F18106@superduper.net> <728D55C2-2B57-4C4E-9497-A1461FD3AB3F@timhiggins.com> X-Mailer: Apple Mail (2.3608.40.2.2.4) X-Spam-Score: -2.9 (--) Subject: Re: [Make-wifi-fast] wavedroplet 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, 29 Apr 2020 17:09:03 -0000 --Apple-Mail=_D51844DF-06E7-459D-B534-9B530270E3EB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I have not tested Intel captures - they likely use a different set of = rules for time stamping aggregates and until the code handles that they = won=E2=80=99t work. If you can send me a short capture that includes a = few aggregates and I have some spare time I=E2=80=99ll take a look at = adding support. Simon > On Apr 29, 2020, at 4:28 AM, Tim Higgins wrote: >=20 > Capture was made with Intel AX200. I tried all the checkboxes in the = 802.11 Radio panel. None caused the timeline to show up.=20 >=20 > On Apr 28, 2020, at 7:27 PM, Simon Barber > wrote: >=20 >> What was it captured on? It has only been tested with captures from a = MacBook (BCM chipset) and from QCA linux devices. It requires linear = increasing hardware timestamps (there are some bugs in the capture = hardware for both BCM and QCA and sometimes the hardware timestamp has = errors). If it=E2=80=99s a QCA capture the timestamp marks the end of = the frame, not the start of the data field, there is a checkbox in the = preferences to account for that. >>=20 >> Simon >>=20 >>=20 >>> On Apr 28, 2020, at 1:41 PM, Tim Higgins > wrote: >>>=20 >>> I'm on WS 3.2.1 and checked the "Enable Wireless Timeline = (experimental) checkbox under Preferernces > Protocols > 802.11 Radio. >>> I don't see the timeline. >>>=20 >>> On 4/28/2020 2:33 PM, Simon Barber wrote: >>>> Has everyone seen the wifi visualization that I added to Wireshark? = It's experimental and has to be turned on in the 802.11 preferences.=20 >>>>=20 >>>> = https://meraki.cisco.com/blog/2019/02/wireshark-where-did-the-time-go/ = =20= >>>>=20 >>>> Simon=20 >>>>=20 >>>> On April 28, 2020 11:18:15 AM Avery Pennarun = wrote:=20 >>>>=20 >>>>> I'm afraid if you have to ask that, this program might not be for = you :)=20 >>>>>=20 >>>>> There's a script called './start' in the toplevel directory. It=20 >>>>> requires you to have the appengine SDK installed (unfortunately). = In=20 >>>>> retrospect, using appengine for this was a bad idea, but we all = make=20 >>>>> mistakes in our youth. But anyway, you can download the appengine = SDK=20 >>>>> and run a local copy for free, so you don't need actual appengine.=20= >>>>>=20 >>>>> On Tue, Apr 28, 2020 at 12:40 PM Tim Higgins = wrote:=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On 4/28/2020 12:30 PM, Avery Pennarun wrote:=20 >>>>>>=20 >>>>>> On Tue, Apr 28, 2020 at 12:09 PM Dave Taht = wrote:=20 >>>>>>=20 >>>>>> On Tue, Apr 28, 2020 at 8:59 AM Tim Higgins = wrote:=20 >>>>>>=20 >>>>>> So how do you use it and what's the output look like?=20 >>>>>>=20 >>>>>> I downloaded it and opened the index.html file in a browser and=20= >>>>>> it doesn't appear to work.=20 >>>>>>=20 >>>>>> It's been years since I had to dig this deep into the wifi stack.=20= >>>>>> Avery's group produced a lot of cool tools while=20 >>>>>> gfiber was in growth mode, he's since moved onto doing cool = things=20 >>>>>> with wireguard ( https://tailscale.com/ = )and I doubt he's maintaining=20 >>>>>> this anymore. We had lots and lots of other very adhoc tools = lying=20 >>>>>> around... parsing wifi caps is a !@#!!=20 >>>>>>=20 >>>>>> Sorry about that, wavedroplet never quite got to something like=20= >>>>>> release quality. It requires more work.=20 >>>>>>=20 >>>>>> However, it shouldn't just totally fail either :) Perhaps = there's an=20 >>>>>> error visible in the javascript console, or python is emitting a=20= >>>>>> problem somewhere (note that it's a python2 program, not = python3).=20 >>>>>>=20 >>>>>> Actually, now that I think of it, I don't know why there's an=20 >>>>>> index.html at all. You definitely need to run the python backend = and=20 >>>>>> connect to that, which probably renders the index.html as a = template.=20 >>>>>>=20 >>>>>> Have fun,=20 >>>>>>=20 >>>>>> Avery=20 >>>>>>=20 >>>>>> Thanks for the reply. And how do I run the python backend?=20 >>>>> _______________________________________________=20 >>>>> Make-wifi-fast mailing list=20 >>>>> Make-wifi-fast@lists.bufferbloat.net = =20 >>>>> https://lists.bufferbloat.net/listinfo/make-wifi-fast = =20 >>>>=20 >>>>=20 >>>>=20 >>>=20 >>=20 >> _______________________________________________ >> Make-wifi-fast mailing list >> Make-wifi-fast@lists.bufferbloat.net = >> https://lists.bufferbloat.net/listinfo/make-wifi-fast = --Apple-Mail=_D51844DF-06E7-459D-B534-9B530270E3EB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I = have not tested Intel captures - they likely use a different set of = rules for time stamping aggregates and until the code handles that they = won=E2=80=99t work. If you can send me a short capture that includes a = few aggregates and I have some spare time I=E2=80=99ll take a look at = adding support.

Simon


On Apr = 29, 2020, at 4:28 AM, Tim Higgins <tim@timhiggins.com> = wrote:

Capture was made with Intel = AX200. I tried all the checkboxes in the 802.11 Radio panel. None caused = the timeline to show up. 

On Apr 28, 2020, at 7:27 PM, Simon Barber <simon@superduper.net> wrote:

What was it captured on? It has only been = tested with captures from a MacBook (BCM chipset) and from QCA linux = devices. It requires linear increasing hardware timestamps (there are = some bugs in the capture hardware for both BCM and QCA and sometimes the = hardware timestamp has errors). If it=E2=80=99s a QCA capture the = timestamp marks the end of the frame, not the start of the data field, = there is a checkbox in the preferences to account for that.

Simon


On Apr 28, 2020, at 1:41 PM, = Tim Higgins <tim@timhiggins.com> wrote:

=20 =20
I'm on WS = 3.2.1 and checked the "Enable Wireless Timeline (experimental) checkbox under Preferernces > Protocols > 802.11 Radio.
I don't see the timeline.

On 4/28/2020 2:33 PM, Simon Barber wrote:
Has everyone seen the wifi visualization that I added to Wireshark? It's experimental and has to be turned on in the 802.11 preferences.

https://meraki.cisco.com/blog/2019/02/wireshark-where-did-the-time-g= o/

Simon

On April 28, 2020 11:18:15 AM Avery Pennarun <apenwarr@gmail.com> wrote:

I'm afraid if you have to ask = that, this program might not be for you :)

There's a script called './start' in the toplevel directory. It
requires you to have the appengine SDK installed (unfortunately). In
retrospect, using appengine for this was a bad idea, but we all make
mistakes in our youth. But anyway, you can download the appengine SDK
and run a local copy for free, so you don't need actual appengine.

On Tue, Apr 28, 2020 at 12:40 PM Tim Higgins <tim@timhiggins.com> wrote:



On 4/28/2020 12:30 PM, Avery Pennarun wrote:

On Tue, Apr 28, 2020 at 12:09 PM Dave Taht <dave.taht@gmail.com> = wrote:

On Tue, Apr 28, 2020 at 8:59 AM Tim Higgins <tim@timhiggins.com> wrote:

So how do you use it and what's the output look like?

I downloaded it and opened the index.html file in a browser and
it doesn't appear to work.

It's been years since I had to dig this deep into the wifi stack.
Avery's group produced a lot of cool tools while
gfiber was in growth mode, he's since moved onto doing cool things
with wireguard ( https://tailscale.com/ )and I doubt = he's maintaining
this anymore. We had lots and lots of other very adhoc tools lying
around... parsing wifi caps is a !@#!!

Sorry about that, wavedroplet never quite got to something like
release quality. It requires more work.

However, it shouldn't just totally fail either :)  = Perhaps there's an
error visible in the javascript console, or python is emitting a
problem somewhere (note that it's a python2 program, not python3).

Actually, now that I think of it, I don't know why there's an
index.html at all. You definitely need to run the python backend and
connect to that, which probably renders the index.html as a template.

Have fun,

Avery

Thanks for the reply. And how do I run the python backend?
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@lists.= bufferbloat.net
https://lis= ts.bufferbloat.net/listinfo/make-wifi-fast





_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/make-wifi-fast

= --Apple-Mail=_D51844DF-06E7-459D-B534-9B530270E3EB--