- ripe-atlas - mailman.ripe.net

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 15 May '22

15 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

My probe's not doin' IPv6
by Edward Lewis 23 Apr '22

23 Apr '22

General question… My probe was doing IPv6 until 15 July 2021 but not it is not. Is there any way to discover why it is no longer IPv6’ing? I did change my ISP connection equipment about that time, so something did change on my end. But IPv6 works for other devices. When I go to www.ripe.net <http://www.ripe.net/> it tells me I came from an IPv6 address. The device has been pretty steady - 99.71% the last week, 99.91% for the last month (30days). It was off-line 29 minutes earlier today (the notice made me think to look), but never off line more than 10 minutes since mid-July. There’s one stretch of 34d+ of continuous uptime. Run-of-the-mill home connection via a cableTV company. Is there anyway to ask a probe why it doesn’t have an IPv6 address (via DHCP)? Ed

5 7

TLSv1.3 Support
by Antonios Chariton 23 Apr '22

23 Apr '22

I’ve ran a measurement against a host that only support TLSv1.3 ( https://atlas.ripe.net/measurements/40393656/#probes ) and all probes came back with "Error: protocol_version”. Do they not support the latest version of TLS? I only seem to be able to get them to work with TLSv1.2 or lower. Thanks, Antonios

1 0

json with all probes
by Cristel Pelsser 23 Apr '22

23 Apr '22

Hi, Can someone point me to the location of the json file with all the probes and their properties? Cristel

2 2

Moving on
by Philip Homburg 06 Apr '22

06 Apr '22

Hi Atlas Users, After ten years at the RIPE NCC it is time for me to move on. Normally, that is not something that would be announced on a public mailing list. However, I get quite a bit of email that is directly sent to me. This is to let you know that I will not be able to read future email sent to this address. I have two new colleagues who will work on probe firmware development. They are Guy Meyer <gmeyer(a)ripe.net> and Michel Stam <mstam(a)ripe.net>. I'm sure they will be happy to help. As for me, I will be <philip(a)nlnetlabs.nl> from now on. Philip Homburg

3 2

RIPE Atlas Quarterly Planning Q2 2022
by Robert Kisteleki 31 Mar '22

31 Mar '22

Dear colleagues, We are now publishing our quarterly planning for RIPE Atlas. This is available at: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and hear what you would like to see the RIPE NCC work on going forward. We will provide status updates as the work progresses and add input from the community to the pages. We will also archive previous plans so you can track how we progress with 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

New on RIPE Labs: Bias in Internet Measurement Infrastructure
by Alun Davies 28 Mar '22

28 Mar '22

Dear colleagues, In this new article on RIPE Labs, Pavlos Sermpezis talks about analysing bias in the Internet measurement infrastructures like RIPE Atlas and RIPE RIS. Are these infrastructures biased? How much of a problem is it if they are? What does bias even look like here? Find out more: https://labs.ripe.net/author/pavlos_sermpezis/bias-in-internet-measurement-… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0