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] Selecting only anchors for UDM
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Using RIPE Atlas to Debug Network Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Strikos
astrikos at ripe.net
Wed Jun 11 12:25:39 CEST 2014
Hi Ondřej, there is already an API only flag that is similar to what you want. Its behavior is a bit different from what you want though, since it will try to fetch anchors first and if we don't have enough the rest will be covered by normal probes. Would that be sufficient for your needs? It's not stated on the docs and we use it currently only for our internal needs. It makes sense now though to give it to public as well. There is some cleaning up to be done first so it will be out with one of our next releases. Regards, Andreas On 6/11/14, 12:03 PM, Ondřej Caletka wrote: > Hello list, > > is there a way to run an UDM on Anchors only? I think it would be a good > feature, especially for precise latency measurement. > > Cheers, > Ondřej Caletka >
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Using RIPE Atlas to Debug Network Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]