Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: question concerning traceroute?

  • From: Jared Mauch
  • Date: Thu Oct 17 11:00:10 2002

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.




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.