[Outages-discussion] META: Tracing outages and paths

[Jeremy Chadwick]

On Wed, May 11, 2011 at 06:41:53PM -0500, Chris Adams wrote:
> 179.60.1305153937053.JavaMail.root at benjamin.baylink.com>
> In-Reply-To: <32503179.60.1305153937053.JavaMail.root at benjamin.baylink.com>
> 
> Once upon a time, Jay Ashworth <jra at baylink.com> said:
> > Just a reminder: if you're having trouble with access to a service over the
> > internet (and you don't already know this; gimme a break :-), one of the
> > most useful bits of data you can provide in your report is a traceroute,
> > and (my favorite) tool for this is mtr.  The Linux version is probably
> > a bit more useful than the Windows version, but both are available, and
> > provide better statistical data than the standard traceroute, or ghod
> > forbid, just a ping (RIPMM).
> 
> mtr is also available on Juniper routers since JUNOS 8.something IIRC,
> either from the shell, or from the CLI.
> 
> > I usually use:
> >
> > # mtr -r 10 -c hostname.example.com
> 
> JUNOS CLI: traceroute monitor count 10 hostname.example.com
> 
> > # mtr -r 10 -c -n hostname.example.com
> 
> JUNOS CLI: traceroute monitor count 10 no-resolve hostname.example.com

Awesome.  This is something I've been wanting for a while.  Does it
support MPLS label decoding like JunOS traceroute?

I'm a little surprised that the mtr (at least from the shell) is v0.69,
which is extremely old and I believe has very serious security holes.

-- 
| Jeremy Chadwick                                   jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.               PGP 4BD6C0CB |