This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Concurrent traceroute issues on the probes
- Previous message (by thread): [atlas] Concurrent traceroute issues on the probes
- Next message (by thread): [atlas] Concurrent traceroute issues on the probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Jul 23 14:04:45 CEST 2012
On 7/23/12 10:57 , David Lebrun wrote: > 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 ? > 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.
- Previous message (by thread): [atlas] Concurrent traceroute issues on the probes
- Next message (by thread): [atlas] Concurrent traceroute issues on the probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]