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: alex
  • Date: Thu Oct 17 11:18:04 2002

> > > > > 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.
> 
> 	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.


That, obviously, is correct. 

	However, the remote ip in this case is your local IP, so you are
still getting a path to the destination.
	
	Even more importantly, LSR relies on every router on a forward path 
between <your-local-ip> and <remote-router-before-host> allowing LSR, which
is an invalid assumption.


Thanks,
Alex






Discussion Communities


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


Merit Network, Inc.