From: "Fred Baker (fred)" <fred@cisco.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "<codel@lists.bufferbloat.net>" <codel@lists.bufferbloat.net>,
"<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] blip: a tool for seeing internet latency with javascript
Date: Sun, 28 Apr 2013 23:53:49 +0000 [thread overview]
Message-ID: <8C48B86A895913448548E6D15DA7553B829BF1@xmb-rcd-x09.cisco.com> (raw)
In-Reply-To: <CAA93jw4isN-jzwERwPRBv_e2AFm2TUz-vLxXd_WN7acXmYBGxA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]
On Apr 26, 2013, at 4:04 PM, Dave Taht <dave.taht@gmail.com<mailto:dave.taht@gmail.com>> wrote:
Apenwarr has developed a really unique tool for seeing latency and
packet loss via javascript. I had no idea this was possible:
http://apenwarr.ca/log/?m=201304#26
Indeed, very cool.
For those on PCs running Windows, there is also pingplotter (http://www.pingplotter.com). It sends what amounts to a trace route once a second - a burst of packets back to back with TTLs varying from 1 to the number of hops between you and whatever you're targeting. It tracks not only the end to end behavior but the behavior along the way. If you like, you can leave it running and have it send you an email with a .png of an event that is worse than some threshold. I've attached a graphic it showed me once about a particular path I cared about that happened to have a geosynchronous satcom delay in it.
BTW, the data here is most definitely dated. A ping I just did gave me
--- 212.88.97.49 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 364.163/372.373/398.910/5.712 ms
[cid:717DCED7-6136-433E-A8A4-9FF5795D689A@cisco.com]
[-- Attachment #1.2: Type: text/html, Size: 1924 bytes --]
[-- Attachment #2: sb-to-ug.distrouter.mtn.co.ug.jpg --]
[-- Type: image/jpeg, Size: 176091 bytes --]
next prev parent reply other threads:[~2013-04-28 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:04 [Cerowrt-devel] " Dave Taht
2013-04-28 14:56 ` [Cerowrt-devel] [Bloat] " Rich Brown
2013-04-28 18:02 ` Maciej Soltysiak
2013-04-28 23:53 ` Fred Baker (fred) [this message]
2013-04-28 18:52 dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8C48B86A895913448548E6D15DA7553B829BF1@xmb-rcd-x09.cisco.com \
--to=fred@cisco.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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