[40845] in North American Network Operators' Group
Re: Measuring PoP to PoP latency--tools to use?
daemon@ATHENA.MIT.EDU (Christopher A. Woodfield)
Thu Aug 23 12:54:20 2001
Date: Thu, 23 Aug 2001 12:53:52 -0400
To: Brian <bri@sonicboom.org>
Cc: nanog@merit.edu
Message-ID: <20010823125352.F7846@semihuman.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009d01c12be9$2b1bc8a0$3324200a@sonicboom.org>
From: "Christopher A. Woodfield" <rekoil@semihuman.com>
Errors-To: owner-nanog-outgoing@merit.edu
Both C&W and Digex/Intermedia had websites that showed this information.
However, this was only shows within that provider's network, not to other
networks.
-Chris
On Thu, Aug 23, 2001 at 08:33:56AM -0700, Brian wrote:
>
> I once worked for a company that wrote a unix script that worked like this.
> Basically imagine a quare chart will all the pops listed across the top and
> down the left side. Every few minutes, each pop tries a small ping burst to
> ping all of the others, and the values are filled into the chart. Results
> are color coded as green, yellow, and red.
>
> Brian
>
> ----- Original Message -----
> From: "Sam Thomas" <sthomas@lart.net>
> To: "mike harrison" <meuon@highertech.net>
> Cc: "Grant A. Kirkwood" <grant@virtical.net>; "Sean Donelan"
> <sean@donelan.com>; <nanog@merit.edu>
> Sent: Thursday, August 23, 2001 7:27 AM
> Subject: Re: Measuring PoP to PoP latency--tools to use?
>
>
> >
> > when someone asked me to do something like this, i waded through caida's
> > site and came accross this:
> >
> > http://www-iepm.slac.stanford.edu/pinger/
> >
> > it's pretty cool stuff. requires *nix box, perl5, and some sort of
> > webserver software to produce simple reporting. there's also (optionally)
> > utilities that draw some pretty graphs that require gnuplot/ppmtogif.
> >
> > imho, this is considerably better than logging into your router to do
> this.
> > routers are much better at forwarding packets than sending/receiving
> > them. (except older non-distributed routers, which aren't particularly
> > great at either for high traffic volumes) other bonus: no automated
> sending
> > of passwords from a box that might not get much admin attention.
> >
> > one could probably modify these tools to use fping, but i just played
> > around with them for edutainment purposes. there's no mention of copyright
> > that i can find, but one should ask before using for commercial purposes.
> >
> > On Thu, Aug 23, 2001 at 08:32:17AM -0400, mike harrison wrote:
> > >
> > > > It was cheesy, and not particularly scientific, but I've been trying
> to
> > > > find something like that to implement for the marketing folk. It could
> > > > probably be adapted into something more useful to us though. Suffice
> it
> > >
> > > fping, from Stanford originally, now at www.fping.com
> > > might be useful, it pings multiple hosts at the same time
> > > (fast, efficient) It has easy to parse output and easily gives results
> > > like:
> > >
> > > fping -e <targets
> > > www.chatt.net is alive (0.32 ms)
> > > www.att.net is alive (27.5 ms)
> > > www.uu.net is unreachable
> >
> > --
> > Sam Thomas
> > Geek Mercenary
> >
>
--
---------------------------
Christopher A. Woodfield rekoil@semihuman.com
PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B
