From: Jim Gettys <jg@freedesktop.org>
To: Kathleen Nichols <nichols@pollere.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] passive network delay monitoring utility
Date: Tue, 23 May 2017 15:22:03 -0400 [thread overview]
Message-ID: <CAGhGL2DURpvkK4TXjMeUOnUo=NmMH2HeHzBTx8JwkusBTdn-1w@mail.gmail.com> (raw)
In-Reply-To: <68972d45-9112-6202-7e6d-7dfc7349530b@pollere.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Those of you who have not looked at pping should do so.
See: http://pollere.net/pping.html for a description, and look at the
slides linked to on that page.
In particular, it would be sweet to run this on a home router, as you can
monitor latency simultaneously in either direction. Then we can point a
finger properly at the ISP or at the WiFi in the home network (encouraging
either/both to get fixed).
Anyone interested in undertaking such a project with me, please drop me a
note.
The only downside is that pping is a C++ app, which makes it big for a home
router, so it can't be used on old small home routers due to footprint
issues; but many current home routers would have space for it.
- Jim
On Sun, Apr 30, 2017 at 8:41 PM, Kathleen Nichols <nichols@pollere.com>
wrote:
>
> Hi,
> I've just made one of the tools I use to measure network delay
> available with a GPLv2 license. Perhaps it will be of intererst.
>
> https://github.com/pollere/pping
>
> Kathie
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2653 bytes --]
next prev parent reply other threads:[~2017-05-23 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 0:41 Kathleen Nichols
2017-05-23 19:22 ` Jim Gettys [this message]
2017-05-23 19:50 ` Eric Dumazet
2017-05-26 17:31 ` Kathleen Nichols
2017-05-26 18:41 ` Kathleen Nichols
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGhGL2DURpvkK4TXjMeUOnUo=NmMH2HeHzBTx8JwkusBTdn-1w@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=bloat@lists.bufferbloat.net \
--cc=nichols@pollere.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