Concurrent traceroute issues on the probes
Hi all, I was wondering whether the probes can perform multiple concurrent traceroutes toward different destinations, and if so, are they able to differentiate the replies ? I just ran into this problem with paris-traceroute, the path were completely mixed up and stderr output looking like the following messages multiple times (IP addresses redacted): [WARN](TracertImpl.cc, 368)A reply received with bad original destination address A.B.C.D, should be W.X.Y.Z [WARN](TracertImpl.cc, 326)Bad return flow id 0x4d2 from E.F.G.H [WARN](TracertImpl.cc, 331)ICMP reserved words 0 0 0 0 0 As the probes use paris-traceroute, I prefer to be sure that the results are not flawed. David
On 7/23/12 8:15 , David Lebrun wrote:
I was wondering whether the probes can perform multiple concurrent traceroutes toward different destinations, and if so, are they able to differentiate the replies ?
Yes, which instance it is, is encoded in the packet that is sent out.
On 07/23/2012 05:28 PM, Philip Homburg wrote:
Yes, which instance it is, is encoded in the packet that is sent out.
Ok thanks. This leads me to another question: do you use the standard paris-traceroute arguments to perform this or is it a customized version ? The actual question might be: how is the instance ID encoded in the packet ?
On 7/23/12 10:57 , David Lebrun wrote:
Yes, which instance it is, is encoded in the packet that is sent out. Ok thanks. This leads me to another question: do you use the standard
On 07/23/2012 05:28 PM, Philip Homburg wrote: paris-traceroute arguments to perform this or is it a customized version ? The actual question might be: how is the instance ID encoded in the packet ?
I didn't try to follow existing traceroute implementations. There are now 8 variations of traceroute: v4/v6 UDP/ICMP paris or non-paris. For v4/UDP/paris, the instance id is put in the source port.
On 07/23/2012 09:04 PM, Philip Homburg wrote:
I didn't try to follow existing traceroute implementations.
There are now 8 variations of traceroute: v4/v6 UDP/ICMP paris or non-paris. For v4/UDP/paris, the instance id is put in the source port.
Okay, thanks for your answers !
participants (2)
-
David Lebrun -
Philip Homburg