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] Question about built-in first/second hop latency measurements
- Previous message (by thread): [atlas] Question about built-in first/second hop latency measurements
- Next message (by thread): [atlas] Feature Request to consider: DNS response IP header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Mon Jul 22 13:24:48 CEST 2019
Hi Joel, Results from measurements 1 and 2 are really the first and second hops of a single traceroute measurement with a max_hops value of 2. Regards, Chris Amin RIPE NCC On 22/07/2019 00:16, Joel Sommers wrote: > Hello all, > > For the built-in latency measurements to first/second hops, my assumption has pretty much always been that these are done with hop-limited probes (i.e., with TTL or hop limit set to 1 or 2). Is that true, or are these measurements taken using “direct” pings? > > Thanks! > > Joel > > >
- Previous message (by thread): [atlas] Question about built-in first/second hop latency measurements
- Next message (by thread): [atlas] Feature Request to consider: DNS response IP header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]