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] Probe with ever changing upstreams/ASs?
- Previous message (by thread): [atlas] Probe with ever changing upstreams/ASs?
- Next message (by thread): [atlas] Probe with ever changing upstreams/ASs?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Thu Aug 3 19:53:41 CEST 2023
Hi Carsten, > Anyhow: as part of this tunnel setup, the other end of the tunnel > changes every 24 to 48 hours - and so does the upstream and therefore > also the AS of the upstream provider. I think the short answer is: probably not highly useful. But of course it depends :-) Each result is tagged with the (then) source IP of the probe, as far as the infrastructure knows that. For argument's sake let's say that is the IP where the probe is otherwise connecting from. If that IP, because of the tunnels, changes regularly, then it's ... kind of ok, results from different days will vary both in RTT and in source IP (and in actual content. eg. DNS or TLS results). However, if the probe's IP stays stable but the results vary each day, then it's may be confusing to interpret. At the end of the day, measurements involving this probe would give varying results depending on time. It's totally real, but is it useful? Cheers, Robert
- Previous message (by thread): [atlas] Probe with ever changing upstreams/ASs?
- Next message (by thread): [atlas] Probe with ever changing upstreams/ASs?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]