Re: [atlas] V5 probes

[Niall O'Reilly]

On 6 Oct 2022, at 11:11, Daniel AJ Sokolov wrote:

> That's pretty cool!

+1

> So my v1 is not that rare, given there are still some 440 connected.

-1; mine died ...

Niall

-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Tagging probes which are using the ISP's DNS server?

[Niall O'Reilly]

On 6 Oct 2022, at 13:32, Simon Brandt via ripe-atlas wrote:

If the distinction isn't to difficult to implement, I would prefer 
these three types as system tags:


Inside-AS DNS
Outside-AS DNS
RFC1918 DNS


At least these are necessary,
but I'm not sure that they are sufficient.

For example, "Inside-AS" masks the distinction between on-site
and ISP-provided resolvers, which are distinct on my domestic
network (RFC1918 + GLA) and still (I believe) on the campus
network where I once had a day job (Gv4 + GLA).

Apart from that, should there be separate tags for RFC1918
and ULA?

€0,02
Niall

--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] API error

[Chris Amin]

Dear colleagues,

The issue with the latest and results endpoints not working for 
restricted built-in measurements has now been resolved. You should now 
be able to see results for public probes and probes hosted by you on 
these endpoints.


Apologies again for the inconvenience.

Regards,
Chris

On 26/09/2022 15:58, Ernst J. Oud wrote:


Hi,

Since a short while (1 or 2 days) I get an authorization error when 
downloading the data from the built-in first and second hop to 
ping.ripe.net.


Thus:

https://atlas.ripe.net/api/v2/measurements/1/results/?probe_ids=1004467&start=1664150400&stop=1664236799&format=json


Gives:

{"error":{"detail":"Authentication credentials were not 
provided.","status":403,"title":"Forbidden","code":104}}

If I logon with my credentials via “My Atlas”, I get:

{"error":{"detail":"You do not have permission to perform this 
action.","status":403,"title":"Forbidden","code":104}}


All other tests let me download the data fine, logged in or not.

Same happens to download first and second hop data of other public probes.

Any clues?

Regards,

Ernst J. Oud



--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas