On Thu, 17 Oct 2002, k claffy wrote:
> remark it is also possible for the (forward or reverse)
> path to change in the middle of the measurement,
> such that traceroute output would lead you
> to believe a path that never existed anywhere
> on the Internet (i.e., one that is not manifested
> in th
On Thu, Oct 17, 2002 at 10:31:12AM -0400, Darrell Carley <[EMAIL PROTECTED]>
wrote:
> I am trying to troubleshoot a latency issue for some of our networks,
> and was wondering about this.Knowing that routing isn't always
> symmetrical, is it possible for a traceroute to traverse a different
> re
> > > > > 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.
>
On Thu, Oct 17, 2002 at 08:43:01AM -0700, k claffy wrote:
>
> remark it is also possible for the (forward or reverse)
> path to change in the middle of the measurement,
> such that traceroute output would lead you
> to believe a path that never existed anywhere
> on the Internet (i.e., one that i
at Thursday, October 17, 2002 3:58 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> was seen to say:
>> Unless you did "- g",
> Not correct. -g specifies loose source routing on the way *there*,
> not back.
No, you can get both if you ping *yourself* with the actual destination
as -g. this gives you both
On Thu, Oct 17, 2002 at 07:45:39AM -0700, Stephen Stuart wrote:
Traceroute sends UDP datagrams and receives ICMP datagrams in order to
show you what it shows you. It is possible for the ICMP datagrams to
return via a different path than the UDP datagrams took outbound (it
is also possi
> a traceroute shows the outbound route. it's possible for the the probe
> packets to follow one path and the returning icmp packets to take another
> path. a looking glass in the AS your tracing to is a good way to see what
> the return path is...
The returning ICMP packets may take many differe
There used to be an old flag you could set on an
ICMP_ECHO request to record the path the echo reply takes back (ping -R or -r?),
but apparently its not used much anymore. Probably just as well.. it could only
hold ~8 hops..
Andy
- Original Message -
From:
Darrell Carley
$author = "Darrell Carley" ;
>
> I am trying to troubleshoot a latency issue for some of our networks,
> and was wondering about this.Knowing that routing isn't always
> symmetrical, is it possible for a traceroute to traverse a different
> reverse path, than the path that it took to get there?
On Thu, Oct 17, 2002 at 10:58:03AM -0400, [EMAIL PROTECTED] wrote:
>
> > [EMAIL PROTECTED] 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
> [EMAIL PROTECTED] 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 t
[EMAIL PROTECTED] 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.
> I am trying to troubleshoot a latency issue for some of our networks,
> and was wondering about this.Knowing that routing isn't always
> symmetrical, is it possible for a traceroute to traverse a different
> reverse path, than the path that it took to get there?
Traceroute sends UDP datagrams
> 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.
Alex
14 matches
Mail list logo