[40826] in North American Network Operators' Group
Re: Measuring PoP to PoP latency--tools to use?
daemon@ATHENA.MIT.EDU (Sam Thomas)
Thu Aug 23 10:29:49 2001
Date: Thu, 23 Aug 2001 14:27:15 +0000
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" <nanog@merit.edu>
Message-ID: <20010823142715.A28586@lart.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.10.10108230824260.14477-100000@home.highertech.net>; from meuon@highertech.net on Thu, Aug 23, 2001 at 08:32:17AM -0400
Errors-To: owner-nanog-outgoing@merit.edu
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
