December 2019 - ripe-atlas - mailman.ripe.net

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

Meta-information dumps for built-in measurements?
by Vasileios Giotsas 09 Nov '20

09 Nov '20

Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)? I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/ I guess using the API is an alternative but it would be more convenient to have such dumps Thanks, Vasileios

15 24

One-off measurements not terminating
by Steve Gibbard 30 Dec '19

30 Dec '19

Hi Atlas folks, I hope you’re having a good holiday season. Sorry to interrupt it by complaining about issues. On Christmas Eve my time (early Christmas morning your time) there was an Atlas issue where any attempt at reading measurements failed with an HTTP 500 status error. That appears to have gotten fixed on Christmas (a really big thank you to whoever worked on that) but since then it appears that while most of the one-off measurements we’ve created have delivered results very quickly, none of the measurements created since 17:00 UTC on 2019-12-25 have stopped running. As shown in the Atlas portal: 23722197 Traceroute www.globaltraceroute.com (AS13335) Test Traceroute 1 one-off 2019-12-25 22:24 Never 23722089 Traceroute archive.ubuntu.com (AS41231) Test Traceroute 1 one-off 2019-12-25 19:16 Never 23722088 Traceroute sps.prima.com.ar (AS10318) Test Traceroute 1 one-off 2019-12-25 19:14 Never 23721915 Traceroute www.globaltraceroute.com (AS13335) Test Traceroute 1 one-off 2019-12-25 17:00 Never And on for every measurement between then and now. Previously, the typical one-off measurement was listed with start and stop times less than 10 minutes apart. When a user has 100 measurements running concurrently, creation of new measurements fails, which is happening for me now. If somebody could take a look at this, I’d really appreciate it. Thanks, Steve

2 3

Deletion of erroneously scheduled measurements
by Nils Rodday 29 Dec '19

29 Dec '19

Dear Atlas folks, I have accidentially scheduled many faulty measurements via the API and am now looking for a way to remove them in order to minimize unnecessary burden on the Atlas system and not to pollute my account & limits with unnecessary measurements. However, the DELETE statement (AtlasStopRequest) only seems to be able to stop ongoing measurements [1]. I always get the following reply trying to remove any future measurement: {'error': {'detail': 'That measurement cannot be stopped', 'status': 400, 'title': 'Bad Request', 'code': 104}} Also, the AtlasChangeSource & AtlasChangeRequest of Cousteau [2] can only change ongoing experiments (as I wanted to set the probes in each measurement to 1 if I wasn´t allowed to delete any of them). But since they are upcoming, but not ongoing, I could also not alter them. I am also referring to a mailing-list post from October 2013 stating essentially the same problem [3]. Given the significant amount of time that has passed since then I wanted to raise this issue again. Is there any way to delete a measurement that is in the "SPECIFIED" state, which means that it will only be executed in the future? I understand that we might want to avoid deletion of measurements that have already been run in the past in order to allow others to benefit from the results, but why shouldn´t one be allowed to eliminate faulty measurements that have been scheduled by accident in the future? Thanks & a Happy New Year! Kind regards, Nils [1] https://atlas.ripe.net/docs/api/v2/manual/measurements/stop-measurements.ht… [2] https://ripe-atlas-cousteau.readthedocs.io/en/latest/use.html [3] https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-October/001058.html

1 0

measurement page broken?
by Dave . 16 Dec '19

16 Dec '19

Hi, I just started 2 measurements like 10 minutes ago but it does seem something broke. https://atlas.ripe.net/measurements/23631307/#!probes Same issue here: https://atlas.ripe.net/measurements/23631303/#!probes I get to see a spinner instead of the results. Thanks, Dave

2 5

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