- ripe-atlas - mailman.ripe.net

Letsencrypt certificates on anchors
by Anand Buddhdev 13 Dec '19

13 Dec '19

Dear colleagues, Some time ago, there was discussion on this list about deploying Letsencrypt certificates on anchors. We had said we would investigate the possibility of doing this. We are pleased to report that we have worked out how to do this seamlessly. Early next week, all RIPE Atlas anchors will switch to Letsencrypt certificates. Note that we will re-use the existing keys on the anchors to request the Letsencrypt certificates. The TLSA records of all anchors are pinned to these private keys, and so they will not change. Regards, Anand Buddhdev RIPE NCC

3 2

Anchor VM security
by Rami Al-Dalky 12 Dec '19

12 Dec '19

Hi, If someone is planning to host a VM anchor, what are the security measures that RIPE Atlas can provide? For example, protecting the VM from being compromised by an attacker. Any information about this is highly appreciated because the plan is host several anchors. Thanks, Rami

2 1

Probes connected to 4G/LTE
by Ponikierski, Grzegorz 06 Dec '19

06 Dec '19

Hi all! I'm thinking about becoming ambassador to deploy more probes in Poland including rural areas where sometimes the only option to get access to the Internet is 4G/LTE. I'm interested what is your experience with 4G/LTE and Atlas probes. What tags you use to mark them? How stable they are? What RTT you see to first and second hop? Regards, Grzegorz

3 2

Long measurement delays
by Steve Gibbard 30 Nov '19

30 Nov '19

Hello, Atlas crew, I’ve been seeing delayed query responses to one-off measurements since November 22, with the exception of November 25. For www.globaltraceroute.com, which attempts to get responses for 90 seconds after submitting a query (and is usually fairly successful), this has meant a failure rate of 61% on average for those days, and as high as 83% on one of the days. I haven’t been tracking how long it does take for a response to come in in those cases, but my most recent test measurement, measurement ID 23502037, is still not returning any data an hour and 40 minutes after submission. My request format as a Python string is "https://atlas.ripe.net/api/v2/measurements/%s/latest/?key=%s" % (measurement_id, key). For these failures I’m receiving an empty list, so it looks like this might be something different than the “synchronizing” issue people were complaining about over the last few weeks. Trying to access that measurement via the Atlas Web UI, if I go to the “latest results” tab I get a spinning progress wheel, seemingly forever. I haven’t been tracking the Atlas “consumption delay” along with the results, so I’m not sure what it’s looked like during most of the failure periods. I checked at the time I submitted measurement 23502037 and it showed as green, although it’s showing as yellow now. Thanks for any help or attention you can provide on this. -Steve

3 2

Measurements "synchronizing"
by Stephane Bortzmeyer 30 Nov '19

30 Nov '19

It seems that, today, when querying the API about an existing measurement, I always get: {'id': None, 'name': 'synchronizing'} Which I've never seen. (Measurement #23238335 but it's not the only one.) A recent change? A temporay problem?

2 5

swagger spec 2.0
by av＠ipmn.io 30 Nov '19

30 Nov '19

Hi, I can't write to the previous post about swagger, so created the new one. I made some tooling auto conversion from 1.2 to 2.0 and a little bit of hand fixing to current spec. It would be nice if anybody could help with getting 2.0 version up to date. Here is what I have for now: https://app.swaggerhub.com/apis/akme/ripe-atlas_api_reference/v2.4.0

1 0

Unable to set probe location to Hong Kong
by Ponikierski, Grzegorz 28 Nov '19

28 Nov '19

Hi all! I was wondering why I see more probes in Hong Kong marked as Chinese probes. For test, I tried to set location of my probe to Hong Kong and even if I put location pin on map in the middle of Hong Kong it still ends assigned to China. Are we still able to assign RIPE Atlas probes to Hong Kong? If not, then what about probes which are still assigned to Hong Kong? How to reliably get via API list of probes located in Hong Kong? Should we parse geo coordinates and use 3rd party libraries to figure out where probe is really located? Regards, Grzegorz

2 2

Finding the NSID in the measurement results
by Roger Murray 28 Nov '19

28 Nov '19

Dear colleagues, We have a measurement with the NSID flag set to True: https://atlas.ripe.net/measurements/23444279/#!general and we are seeing the NSID responses in the web-gui for the measurement: https://atlas.ripe.net/measurements/23444279/#!probes So far so good, but when we download the raw measurement result data we are not able to locate the NSID information. We would really appreciate any help in finding the NSID in the result information. Thanks in advance, /rog The Swedish Internet Foundation https://internetstiftelsen.se/en/

2 1

Fwd: Probe 2317 is disconnected (home fibre)
by Colin Johnston 14 Nov '19

14 Nov '19

Any idea why went disconnected today, I think came back ok though AS connectivity was ok whilst probe said down though.. Any chance of enhancement to send email once connected again ? Connected (UTC) Connected for Disconnected (UTC) Disconnected for 2019-11-14 12:43:47 2h 13m Still Connected 2019-11-14 12:33:17 0h 0m 2019-11-14 12:33:49 0h 9m 2019-11-14 02:50:45 8h 49m 2019-11-14 11:39:46 0h 53m 2019-11-08 16:42:22 5d 9h 45m 2019-11-14 02:28:01 0h 22m 2019-11-08 13:19:26 3h 15m 2019-11-08 16:34:53 0h 7m 2019-11-05 12:32:57 2d 7h 34m 2019-11-07 20:07:40 17h 11m 2019-10-15 14:58:43 20d 21h 25m 2019-11-05 12:24:08 0h 8m > Begin forwarded message: > > From: RIPE Atlas (no reply) <no-reply(a)ripe.net> > Subject: Probe 2317 is disconnected (home fibre) > Date: 14 November 2019 at 12:00:01 GMT > To: colinj(a)mx5.org.uk > Reply-To: RIPE Atlas (no reply) <no-reply(a)ripe.net> > > Dear colin johnston, > > Your probe 2317 has been disconnected from the RIPE Atlas infrastructure since 2019-11-14 11:39:46 UTC. > > You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: > > https://atlas.ripe.net/probes/2317/#!tab-status > > Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab and your probe has just gone offline, please check back in a few hours, as more information may be available. > > If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. > > Kind regards, > > RIPE Atlas Team > > ********** > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 10 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications".

2 1

Request: RIPE Atlas Credits for Lab Course
by Trinh Viet Doan 11 Nov '19

11 Nov '19

Hello everyone, I am a PhD student at TUM and would require around 200M credits to perform large-scale measurements for a lab course that we are running with our master students (http://www.cm.in.tum.de/teaching/2019-imarl/ <http://www.cm.in.tum.de/teaching/2019-imarl/>). If you have any credits to share, we would greatly appreciate it! :) Thanks in advance and best regards, Viet

7 9