- ripe-atlas - mailman.ripe.net

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

RIPE NCC Open House: Feedback on our Unified User Interface
by Michela Galante 28 Mar '22

28 Mar '22

Dear colleagues, On Wednesday 6 April from 10:00 to 11:30 UTC, we invite users of RIPE Atlas, RIPE Database, RIPE Labs, RIPE NCC Academy, LIR Portal, RPKI and RIPEstat to give us feedback on our unified user interface. This Open House session will focus on the user interface that was launched in 2020. Our goal is to unify the user experience across all platforms to make it easier and faster for users to navigate our services. You can register for the event at: https://meeting-registration.ripe.net/meeting-pub/registration?0&meetingId=… More information is available on our website: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-fe… Best regards, Michela Galante RIPE NCC

1 0

problem reusing probes
by Cristel Pelsser 28 Mar '22

28 Mar '22

Hi, I have a problem reusing probes from previous measurements. I’m launching experiments in pairs from the web interface. I would like to retrieve the probes selected randomly in one experiment for another measurement that takes place at the same time. My problem is that it takes time to show the measurement I created in the list of "my measurements". Even when all measurements are shown in the list of all "my measurements", the creation interface does not find all these measurement ids. So I cannot retrieve the probes I need. Is there an access problem to the measurement DB or am I doing something wrong? Cristel

1 0

Problem with DoT measurements?
by Stephane Bortzmeyer 24 Mar '22

24 Mar '22

DoT measurements seem partially broken, only 10 % of the probes do report. (See for instance #39675721.)

2 1

Facebook in Russia and a diagnostic problem
by Stephane Bortzmeyer 14 Mar '22

14 Mar '22

Around half of the RIPE Atlas probes in Russia cannot complete a TLS session with facebook.com <https://atlas.ripe.net/measurements/39387725/>. (All the remaining tests have been done with the same set of probes, 'type': 'msm', 'value': '39387725'.) They have no problem with YouTube <https://atlas.ripe.net/measurements/39387839>. I also did TLS tests with IP addresses instead of names, same result <https://atlas.ripe.net/measurements/39387985> <https://atlas.ripe.net/measurements/39388031>. There is no lying DNS resolver <https://atlas.ripe.net/measurements/39387902>. But traceroute show no connectivity problem either, we can go to the Facebook AS from Russia <https://atlas.ripe.net/measurements/39388122> <https://atlas.ripe.net/measurements/39388176>. So, I'm a bit lost: what do we observe? It does not look like censorship but not like a connectivy issue (because of depeering by Cogent and Lumen) either.

6 7

Re: [atlas] Facebook in Russia and a diagnostic problem
by Stephane Bortzmeyer 14 Mar '22

14 Mar '22

On Mon, Mar 14, 2022 at 01:40:02PM +0100, Emile Aben <eaben(a)ripe.net> wrote a message of 21 lines which said: > I find the things the OONI project does very insightful. > > For this particular case: > https://ooni.org/post/2022-russia-blocks-amid-ru-ua-conflict/ Good reference, thanks, it explains everything.

2 1