From: Avery Pennarun <apenwarr@gmail.com>
To: Tim Higgins <tim@timhiggins.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] wavedroplet
Date: Tue, 28 Apr 2020 12:45:25 -0400 [thread overview]
Message-ID: <CAHqTa-3Pr+r5_3VJqhxyeaDEDWkOBaB2i+C_QkbyS41-aiGnwA@mail.gmail.com> (raw)
In-Reply-To: <fe36b582-916c-bf4c-292f-35bc8d65f6e2@timhiggins.com>
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?
next prev parent reply other threads:[~2020-04-28 16:45 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 [this message]
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=CAHqTa-3Pr+r5_3VJqhxyeaDEDWkOBaB2i+C_QkbyS41-aiGnwA@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=dave.taht@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