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/[email protected]/
[atlas] Feature request for Traceroute in RIPE Atlas
- Previous message (by thread): [atlas] New on RIPE Labs: RIPE Atlas WiFi Measurements
- Next message (by thread): [atlas] HTTP measurements at willing targets / protocol suggestion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yue LI
yueli.cnfr at gmail.com
Fri Nov 13 15:52:43 CET 2015
Dear all, So far, the Atlas traceroute is such that if there are 5 consecutive hops with only timeouts (denoted by a star "*"), traceroute will directly try hop 255 and then stop the measurement, which means that the number of total hops can not be obtained. An example can be found: https://atlas.ripe.net/measurements/2841001/#!probes (the probe #22341) Unfortunately, the number of hops is so important to be used as a metric to evaluate the performance of a new protocol. Thus, I propose to add a configuration option for the number of hops after which traceroute decides to call it quits. I wonder whether there are somebody else are also interested in this new feature please? Best regards, Yue -- Yue LI PhD student, Telecom ParisTech Tel: +33 (0)661091840 E-mail: yueli.cnfr at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20151113/35326d7b/attachment.html>
- Previous message (by thread): [atlas] New on RIPE Labs: RIPE Atlas WiFi Measurements
- Next message (by thread): [atlas] HTTP measurements at willing targets / protocol suggestion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]