- ripe-atlas - mailman.ripe.net

Tagging probes which are using the ISP's DNS server?
by Max Grobecker 11 Oct '22

11 Oct '22

Hi, a few days ago I wanted to debug a name resolution problem of one of our domains. For this reason, I wanted to test if probes inside a specific ASN are having difficulties to resolve a specific name (because only customers of this ISP were complaining). This lead to very mixed results, mostly because some of the selected probes did queries to a public DNS service like Google, Quad9 and so on. The problem existed only with the provider's DNS servers for some reason. It did take some time to make a script which tried to filter out these probes, so I wondered if anyone else had the same use-case and problem. Is there a way to automatically tag probes, which are (seemingly) using the ISP's own DNS servers, or, at least, not a well-known public service? This could be done maybe by querying a special DNS name which returns the IP address from where the query was received (like "whoami.akamai.net"). By comparing the ASN of the probe and the ASN of the IP address returned by the DNS query, one could determine, if the ISP's servers are used. This would also be true for people running their own recursor, but this could be filtered as well very easy. If an ISP is using multiple ASN, this could be a problem. Maybe there's an easy solution for this as well. Probes which pass this test, could then be tagged with "DNS-using-ISP-server" or something like that and explicitly be selected for specific DNS resolution tests. Greetings, Max

9 12

v4 Probe Available
by Alexander Burke 10 Oct '22

10 Oct '22

Hello all, I have one more v4 probe available for distribution. If anyone is interested in (reliably!) hosting it, please email me off-list with your address, and I'll get it out to you. First reply gets it. Cheers, Alex

1 0

Revive an abandoned probe?
by Ernst J. Oud 10 Oct '22

10 Oct '22

Hi, As a result of my experiments some three moments ago I have an abandoned probe (OpenWRT). If I power it again will it start working again or do I need te re-apply for a new probe? Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud

3 2

Re: [atlas] V5 probes
by Colin Johnston 07 Oct '22

07 Oct '22

Can someone put me down for a v1 to v5 replacement please ? My v1 at present powered by usb from bt homehub Thanks in advance Colin Sent from my iPod > On 3 Oct 2022, at 12:19, Robert Kisteleki <robert(a)ripe.net> wrote: >

7 9

API error
by Ernst J. Oud 07 Oct '22

07 Oct '22

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&sta… 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

2 2

Re: [atlas] API error
by Ernst J. Oud 05 Oct '22

05 Oct '22

L.S. If for some reason this api error bug takes longer to resolve and the data is important for you, a work around is to download this data from ripestat. Click on the link on your builtins page for the larger graph and click the download button top right. Use this download link to download future data by changing the start and end time in the URL. Reason I use the data from the first hop latency is that my CentOS probe in a VMware Player VM on Windows 10 (bridged) takes 2-3 ms. for the first hop. To get more realistic data for other measurements I subtract this first hop latency data from data of other measurements. Wrote some Freebasic code for this and created my own graphs using the good, old, trusted application ploticus. From the host Windows 10 PC first hop is max 0.5 ms. so the VMware software bridge is not very efficient to get a connection going. If the CentOS VM is kept busy, the first hop is much faster. It is as if Windows and/or VMware suspends/sleeps the thread of the bridge when not active. I searched but did not find any more reports let alone solutions for this weird first hop phenomenon in VMware/Windows environments. Regards, Ernst J. Oud

1 0

Re: [atlas] API error
by Dimeji Fayomi 05 Oct '22

05 Oct '22

Hi, I have also been experiencing this authorization error when I attempt to download first and second hop ping data of public probes. I'd please appreciate any tips or pointers to dealing with this. Thanks Dimeji -- Dimeji Fayomi

2 1

Alternative second hop ?
by Ernst J. Oud 01 Oct '22

01 Oct '22

Hi, On the “Built-ins” tab of the probe dashboard in the drop down list there is a log to download called “Ping Alternative Second Hop”. What is this? It returns an empty data set… BTW… any news on the error when downloading first and second hop data? Regards, Ernst J. Oud

1 0

RIPE Atlas Quarterly Planning Q4 2022
by Robert Kisteleki 27 Sep '22

27 Sep '22

Dear colleagues, The quarterly plans for RIPE Atlas can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas In this quarter, we will start shipping the v5 RIPE Atlas hardware probes to hosts, ambassadors and sponsors as well as continue working on other items proposed by the community. We hope that by providing these plans, we can better inform the community of the ongoing developments on RIPE Atlas and get feedback on our work. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC

1 0

Change in Probe Archive API
by Johan ter Beest 26 Sep '22

26 Sep '22

Dear probe hosts, Since 2013 we are creating a daily snapshot of the probe API which is available at https://atlas.ripe.net/api/v2/probes/archive Until today, this snapshot included some probes which had never connected. Starting with the snapshot of today (26 / 09/ 2022) we will exclude all never connected probes from the archive as they do not provide any useful information. Previous snapshots will not be altered. In addition to this change, every known probe will now have a probestatus page at https://atlas.ripe.net/probes/<probe ID>/ where previously some of these probes would generate a 404. Let us know if you have any question or comment about this change. Kind regards, Johan ter Beest RIPE Atlas Team

1 0