Hi Chris, sorry for "stealing" this conversation, but it's interesting to hear that there will be a redesign of the probe page coming up soon. Can we have a discussion about that? There are several things, that bother me a bit... BR, Simon On 15.12.22 13:51, Chris Amin wrote:
You're right that the probe page is not shown, however the public details are available at https://atlas.ripe.net/api/v2/probes/1003690
The important point there is that the system has not granted the "system: IPv4 Works" tag, so is not available for IPv4 measurements. In general the scheduler doesn't know/care about a probe being marked as public or not.
Can you confirm whether the same measurement request works for IPv6 (af=6) measurements? Note that if you schedule measurements together they must all be IPv6 in that case.
In the meanwhile, we'll think about including the non-public probes (albeit with their somewhat restricted details) as part of a redesign of the probe page coming up soon.
Cheers, Chris
On 15/12/2022 13:12, Ernst J. Oud wrote:
But what is going on then with:
https://atlas.ripe.net/frames/probes/1003690 <https://atlas.ripe.net/frames/probes/1003690>
This probe is within AS15435 and when I list all probes in that AS it is shown, but I cannot add it to a measurement, it is rejected.
Using a curl request to:
stat.ripe.net/data/atlas-probes/data.json?resouce=15435
shows this probe, with a tag “is_public” : false
and I cannot access this probe’s info via the link above, I cannot add it to a measurement and I cannot access any data it collects.
How does this rhyme to that non-public “probes are therefore contributing very nearly as much to the network as everybody else”?