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] Atlas probes in non-production networks
- Previous message (by thread): [atlas] Atlas probes in non-production networks
- Next message (by thread): [atlas] Atlas probes in non-production networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Tue Jul 2 15:24:18 CEST 2024
On Mon, Jul 01, 2024 at 02:30:13PM +0000, Ponikierski, Grzegorz via ripe-atlas <ripe-atlas at ripe.net> wrote a message of 149 lines which said: > RIPE Atlas probes are not tagged and separated into groups that can > be used appropriately for public and internal/private measurements. This is not enirely true, RIPE Atlas probes are tagged, you can ask measurements by including or excluding some tags, and, if (I did not check) the host tagged them with something like "internalnetwork", it solves partially this issue. > Therefore, descripted practice creates another uncomfortable > situation for RIPE Atlas user because there is no way to tell which > probe is deployed in public/production part of the network and which > one in the experimental/non-production one. Can you give the ID of some of these probes so we can check if they have at least a tag?
- Previous message (by thread): [atlas] Atlas probes in non-production networks
- Next message (by thread): [atlas] Atlas probes in non-production networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]