From: Dave Taht <dave.taht@gmail.com>
To: Tim Higgins <tim@timhiggins.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Avery Pennarun <apenwarr@gmail.com>
Subject: Re: [Make-wifi-fast] wavedroplet
Date: Tue, 28 Apr 2020 09:09:07 -0700 [thread overview]
Message-ID: <CAA93jw7O2aJGWCOXm8qnAnTbpgz=A-Cbf4Z+rZXR_SpdXeY0ww@mail.gmail.com> (raw)
In-Reply-To: <3f371367-4535-d29a-4cf2-abca8adb9542@timhiggins.com>
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 !@#!!
> On 4/28/2020 1:05 AM, Dave Taht wrote:
>
> I have a scary feeling I'm going to be ending up deep in wifi captures
> again. Here's one way to get out....
>
> https://github.com/apenwarr/wavedroplet
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-04-28 16:09 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 [this message]
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
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='CAA93jw7O2aJGWCOXm8qnAnTbpgz=A-Cbf4Z+rZXR_SpdXeY0ww@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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