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’t work. If you can send me a short capture that includes a few aggregates and I have some spare time I’ll 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’s 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:

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-go/

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://lists.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