From: Simon Barber <simon@superduper.net>
To: Tim Higgins <tim@timhiggins.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] wavedroplet
Date: Tue, 28 Apr 2020 16:27:34 -0700 [thread overview]
Message-ID: <8283CA5F-D406-47D5-96B3-0F7D21F18106@superduper.net> (raw)
In-Reply-To: <e6791af0-57f1-b96b-99a8-242f5552587b@timhiggins.com>
[-- Attachment #1: Type: text/plain, Size: 3669 bytes --]
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/ <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> <mailto: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> <mailto: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> <mailto:dave.taht@gmail.com> wrote:
>>>>
>>>> On Tue, Apr 28, 2020 at 8:59 AM Tim Higgins <tim@timhiggins.com> <mailto: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/ <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 <mailto:Make-wifi-fast@lists.bufferbloat.net>
>>> https://lists.bufferbloat.net/listinfo/make-wifi-fast <https://lists.bufferbloat.net/listinfo/make-wifi-fast>
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 6756 bytes --]
next prev parent reply other threads:[~2020-04-28 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 5:05 Dave Taht
2020-04-28 15:59 ` Tim Higgins
2020-04-28 16:09 ` Dave Taht
2020-04-28 16:30 ` Avery Pennarun
2020-04-28 16:40 ` Tim Higgins
2020-04-28 16:45 ` Avery Pennarun
2020-04-28 18:33 ` Simon Barber
2020-04-28 18:37 ` Dave Taht
2020-04-28 20:41 ` Tim Higgins
2020-04-28 23:27 ` Simon Barber [this message]
2020-04-29 11:28 ` Tim Higgins
2020-04-29 17:08 ` Simon Barber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8283CA5F-D406-47D5-96B3-0F7D21F18106@superduper.net \
--to=simon@superduper.net \
--cc=apenwarr@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=tim@timhiggins.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox