May 2022 - ripe-atlas - mailman.ripe.net

Requesting Credits for Research
by Alex Gamero-Garrido 29 Jul '23

29 Jul '23

Hi folks, My name is Alexander Gamero-Garrido and I'm a 5th year PhD student at CAIDA, UC San Diego. We're soon launching a large traceroute campaign for research and could use your generous donation of credits. We'll need about 150 million credits, but any partial amount that gets us closer to that goal is welcome and greatly appreciated. My account is agamerog at eng.ucsd.edu Thank you, Alex -- *Alex Gamero-Garrido* *PhD Student, Computer Science* Web: cseweb.ucsd.edu/~agamerog Center for Applied Internet Data Analysis (CAIDA) San Diego Supercomputer Center UC San Diego Pronouns: He/Him/His <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> I'm using Inbox When Ready <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> to protect my focus.

13 15

Probe DHCPv6 support
by Aleksi Pirttimaa 19 May '23

19 May '23

Hi! I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. Do you think a DHCPv6 client should be implemented?

8 13

Overuse of software probes
by Ponikierski, Grzegorz 30 Jun '22

30 Jun '22

Hello all! Software probes is great improvement for Atlas environment and it made deployments so much easier and more scalable. One of my probes is also software probe on Raspberry Pi. However, me and my team noticed that sometimes software probes are overused and make measurements more cumbersome to interpret. For example we found that there 4 software probes in AWS Johannesburg [1] and 15 software probes in Hostinger Sao Paulo [2]. That's total overkill. These 15 probes in Hostinger Sao Paulo is 21% of all connected probes in Brazil. All of them delivers practically the same results so without additional data filtering (which is not easy) they can dramatically skew final results for Brazil. With this I would like to open discussion how to handle this situation. Please share your thoughts about these questions: * How can we standardize data filtering for such case? * How to proactively and automatically detect overuse of probes? * How can we encourage software probes hosts to avoid deployments in data centers which are already covered by Atlas? * How to give incentives to deploy probes in data centers without existing probes? [1] 4 software probes inside AWS Johannesburg: 1000707<https://atlas.ripe.net/frames/probes/1000707/> 1001397<https://atlas.ripe.net/frames/probes/1001397/> 1002066<https://atlas.ripe.net/frames/probes/1002066/> 1002632<https://atlas.ripe.net/frames/probes/1002632/> [2] 15 software probes inside Hostinger Sao Paulo 1003554<https://atlas.ripe.net/frames/probes/1003554/> 1003555<https://atlas.ripe.net/frames/probes/1003555/> 1003556<https://atlas.ripe.net/frames/probes/1003556/> 1003557<https://atlas.ripe.net/frames/probes/1003557/> 1003558<https://atlas.ripe.net/frames/probes/1003558/> 1003559<https://atlas.ripe.net/frames/probes/1003559/> 1003560<https://atlas.ripe.net/frames/probes/1003560/> 1003561<https://atlas.ripe.net/frames/probes/1003561/> 1003562<https://atlas.ripe.net/frames/probes/1003562/> 1003563<https://atlas.ripe.net/frames/probes/1003563/> 1003564<https://atlas.ripe.net/frames/probes/1003564/> 1003565<https://atlas.ripe.net/frames/probes/1003565/> 1003566<https://atlas.ripe.net/frames/probes/1003566/> 1003567<https://atlas.ripe.net/frames/probes/1003567/> 1003568<https://atlas.ripe.net/frames/probes/1003568/> Regards, Grzegorz Ponikierski

13 19

Future of Software Anchors
by Lukas Magauer 04 Jun '22

04 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

Ongoing problem with DoT measurements
by Meikel Kokowski 23 May '22

23 May '22

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

Probe TLS stack
by Christopher Wood 16 May '22

16 May '22

Hi folks, Apologies in advance if the answer to this question is available online somewhere, but I’m wondering if anyone knows what TLS stack is used in Atlas probes, and in particular, what sort of TLS features are configurable by such probes. Best, Chris

2 2

Future of Software Anchors
by ripe.net＠toppas.net 15 May '22

15 May '22

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 2

Atlas probes, IPv6, EUI-64, and privacy
by Alexander Burke 03 May '22

03 May '22

Hello all, I couldn't help but notice that my Atlas probe is using an EUI-64 IPv6 address. It has come to light that the presence of even one device using an EUI-64 address on a network has a negative effect on privacy for the whole network: https://arxiv.org/abs/2203.08946 Thoughts? Cheers and thanks in advance, Alex

2 1