[52812] in North American Network Operators' Group
Re: question concerning traceroute?
daemon@ATHENA.MIT.EDU (Jared Mauch)
Thu Oct 17 10:58:48 2002
Date: Thu, 17 Oct 2002 10:56:59 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: alex@yuriev.com
Cc: "Nipper, Arnold" <arnold@nipper.de>,
Darrell Carley <darrell@national-net.com>, nanog@merit.edu
In-Reply-To: <Pine.LNX.4.10.10210171056390.2640-100000@s1.yuriev.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Thu, Oct 17, 2002 at 10:58:03AM -0400, alex@yuriev.com wrote:
>
> > alex@yuriev.com wrote:
> >
> >
> > >
> > >
> > > > According to definition, is should take the same path, but are there any
> > > > other cases that I should be aware of?
> > >
> > > According to the definition, it is going to show you the path the packets
> > > took from you to the destination, not from the destination back.
> > >
> >
> > Unless you did "- g",
>
> Not correct. -g specifies loose source routing on the way *there*, not back.
Alex,
I think the intention was to indicate that you can
traceroute -g <remote-router-before-host> <your-local-ip>
to get the path to and back. -g requires an argument obviously..
- Jared
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
