- ripe-atlas - mailman.ripe.net

No data for ping to second hop?
by Ernst J. Oud 17 Jun '22

17 Jun '22

Hi, Out of curiosity, all my “Built-ins” in my software probe show data except ”#2 Second Hop to ping.ripe.net (193.0.0.164)” which shows: “No data available for [Probe ID] / 2 for this time period.” Any advice? Regards, Ernst

1 0

Discrepancy in documentation?
by Stephane Bortzmeyer 09 Jun '22

09 Jun '22

[Message already sent on 6 june but it never appeared in my mailbox. Is there some email problem at RIPE?] In the documentation <https://beta-docs.atlas.ripe.net/apis/metadata-reference/>, various HTTP methods are used (for instance DELETE to delete a measurement), which is nice, but the examples ("Try it") always show the method GET.

2 1

How to get DNS return codes and TTLs
by Dallan Adamson 09 Jun '22

09 Jun '22

I'm doing research that requires me to use DNS recursive resolvers around the world. At a minimum from these recursive resolvers I need to know what return code the probe received from the recursive resolver as well as the TTL of the record from the same request. I haven't found a way to get both of these when doing DNS measurements with Ripe Atlas probes, is there a way to do this?

2 1

Future of Software Anchors
by Lukas Magauer 03 Jun '22

03 Jun '22

Hi everybody! I have been running a Software probe on CentOS 8 since mid 2020. (and since switched it to Rocky Linux 8) It’s unsupported, but also didn’t really make any problems, just worked fine with the yum repo distributed package! Great that there are already plans to support newer versions as well! And has there something changed in the distribution of the package? Because the latest changes of version 5070 don’t look like they appeared in the GitHub repo? Best regards, Lukas On 14/05/2022 11:14, ripe.net--- via ripe-atlas wrote: Hi Simon, > So it does not really make sense, to set up a new Anchor with CentOS 7, > i guess. What are the plans, dear RIPE Labs? > I searched the atlas mailinglist topics for "software anchor" and > "centos 7" but didn't find anything. For now, we are still deploying Atlas anchors with CentOS 7. However, in the latter half of this year, we plan to work on adapting our configuration systems to a newer Linux distribution. After that, we will upgrade all the Atlas anchors (hardware and virtual) to the newer distribution. Regards, Anand Buddhdev RIPE NCC Hi everyone, accoring to this site, a CentOS 7 installation is required for running a Software Anchor: https://atlas.ripe.net/docs/anchor-installation-vm/ But CentOS 7 will be End-of-Lifetime in two years (30. Juni 2024). https://wiki.centos.org/About/Product So it does not really make sense, to set up a new Anchor with CentOS 7, i guess. What are the plans, dear RIPE Labs? I searched the atlas mailinglist topics for "software anchor" and "centos 7" but didn't find anything. Greetings, Simon

3 3

Re: [atlas] Ongoing problem with DoT measurements
by Michel Stam 31 May '22

31 May '22

Hi Meikel, Sorry for the silence. I had noticed your issue and apparently forgot to reply we were looking into it. As it is we are, bear with us, I will respond as soon as we have an update. Regards, Michel > On 31 May 2022, at 12:19, Meikel Kokowski <meikel.kokowski(a)stud.uni-hannover.de> wrote: > > Does really no one have any idea or thought concerning this problem? > Anything would be appreciated! > > From: Meikel Kokowski <mailto:meikel.kokowski@stud.uni-hannover.de> > Sent: Tuesday, 24 May 2022 02:48 > To: ripe-atlas(a)ripe.net <mailto:ripe-atlas@ripe.net> > Subject: [atlas] Ongoing problem with DoT measurements > > Dear RIPE Mailing List, > > in the context of my final thesis I am conducting research related to DNS (Do53 and DoT) using RIPE Atlas probes. In preparation for the main measurement I issued, to around 4800 probes, DNS queries > > 1) over TLS [measurement ID: 41196896] and > 2) over Do53 (standard) [measurement ID: 41196980] > > While Do53 works perfectly, DoT seems not to yield any results at all. In the RIPE Atlas forum I found a similar question (https://www.ripe.net/participate/mail/forum/ripe-atlas/PDIwMjIwMzI0MTIzMzE1…). According to that thread, a configuration error on the probes causes the problem. That post is 2 months ago and the problem seems to subsist. Could you provide an update to the current situation to this problem and a possible date for a fix? > > Thank you! > > Best, > Meikel > > -- > ripe-atlas mailing list > ripe-atlas(a)ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas

1 0

Re: [atlas] Ongoing problem with DoT measurements
by Meikel Kokowski 31 May '22

31 May '22

Does really no one have any idea or thought concerning this problem? Anything would be appreciated! From: Meikel Kokowski Sent: Tuesday, 24 May 2022 02:48 To: ripe-atlas(a)ripe.net Subject: [atlas] Ongoing problem with DoT measurements Dear RIPE Mailing List, in the context of my final thesis I am conducting research related to DNS (Do53 and DoT) using RIPE Atlas probes. In preparation for the main measurement I issued, to around 4800 probes, DNS queries 1) over TLS [measurement ID: 41196896] and 2) over Do53 (standard) [measurement ID: 41196980] While Do53 works perfectly, DoT seems not to yield any results at all. In the RIPE Atlas forum I found a similar question (https://www.ripe.net/participate/mail/forum/ripe-atlas/PDIwMjIwMzI0MTIzMzE1…). According to that thread, a configuration error on the probes causes the problem. That post is 2 months ago and the problem seems to subsist. Could you provide an update to the current situation to this problem and a possible date for a fix? Thank you! Best, Meikel

1 0

AS34659
by Jacques Lavignotte 29 May '22

29 May '22

Hi, I may be wrong but it looks like there are 3 probes at ASN34659 (Keyyo) and only 1 is up ? Can anyone confirm ? Thanks, Jacques -- GnuPg : 156520BBC8F5B1E3 Because privacy matters. « Quand est-ce qu'on mange ? » AD (c) (tm)

2 1

Looking for a hardware probe
by Giuseppe Macario 25 May '22

25 May '22

Hello everyone, I would like to host a new Atlas probe (for AS203591) but I understand that RIPE is not shipping probes anymore; I applied online but nobody responded. Therefore, feel free write me an email if you have one for sale, in which case I am willing to pay via PayPal. I will also ask RIPE for a new probe ID, so the history attached to your old probe will be reset. PS: not interested in software probes. -- Giuseppe Macario, PhD https://giuseppemacario.men https://www.giuseppemacario.it

5 4

RIPE-Atlas measurements showed "No recent report available"
by Tingting Lu 25 May '22

25 May '22

Hi all, I am using RIPE-Atlas to generate some ping measurements for my testing ip recently. It worked very well until yesterday. Starting from May 23rd, most of my measurements only have results for a few probes. Most probes showed "No recent report available". Does anyone have the same problem or know what's going on there? -- Regards, Tingting Lu

3 3

RIPE-Atlas measurements showed "No recent report available" [DUP]
by POULET Benoit 25 May '22

25 May '22

Hello, Sorry i can't reply to the already started thread as i'm a new subscriber. I can confirm the problem. I have a lot of measurements with "No recent report available" For examples : https://atlas.ripe.net/measurements/41368751/ https://atlas.ripe.net/measurements/41368760/ https://atlas.ripe.net/measurements/41368768/ It's stared from (UTC+2h) : May 23, 2022 11:28:57 AM

1 0