Re: Traceroute versus other performance measurement

[Andrew Brown <twofsonet () graffiti com>]

> > I need help with a reality/sanity check.   Traceroute is a good tool for
> > checking for routing type problems (loops).  Does anyone feel it's a good tool
>
> It's probably a poor tool for all kinds of really good technical reasons,
> but  "Matts traceroute" aka MTR is useful to me, often shows overstressed
> routers or connections... especially when normal traceroute just shows
> garbage. 

the fact that it does all the probes in parallel, without waiting for
any single probe to time out is definitely a plus.

> Example screen: 
> ...

try mtr with -r (report mode) and -c (number of probe cycles to send)
to get nice little snapshots.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior () daemon org             * "ah!  i see you have the internet
twofsonet () graffiti com (Andrew Brown)                that goes *ping*!"
andrew () crossbar com       * "information is power -- share the wealth."