May 2021 - 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

DNS probes: spurious SERVFAIL
by Lukas Tribus 30 May '21

30 May '21

Dear list, while troubleshooting DNS issues on the Google network yesterday [1] we found that RIPE Atlas probes did not recover after Google fixed the issue, we kept seeing SERVFAIL answers on the RIPE Atlas probes. We now know that those ATLAS results are bogus. For example google.us against 8.8.4.4 https://atlas.ripe.net/measurements/30456676/#probes google.us against 1.1.1.1 https://atlas.ripe.net/measurements/30464549/#probes zoom.us against 8.8.8.8 https://atlas.ripe.net/measurements/30464774/#probes zoom.us against 1.1.1.1 https://atlas.ripe.net/measurements/30464777/#probes amazon.com on quad9 https://atlas.ripe.net/measurements/30479180/#probes amazon.com on quad1 https://atlas.ripe.net/measurements/30479179/#probes Even amazon.com on quad9 and quad1 has numerous SERVFAIL. To reproduce, just try to resolve zoom.us or google.us against 8.8.8.8 or 1.1.1.1 on your probe. Any recommendations on how we could troubleshoot this? [1] https://puck.nether.net/pipermail/outages/2021-May/013648.html

3 4

New on RIPE Labs: Deploying a RIPE Atlas Probe Software via PPP
by Alun Davies 17 May '21

17 May '21

Dear colleagues, Want to install a RIPE Atlas software probe, but not sure how to keep it isolated from your private network? In this new guest post on RIPE Labs, Aris Tzermias demonstrates how to do this using a dedicated PPP connection with your Internet Service Provider. https://labs.ripe.net/author/aris-tzermias/deploying-a-ripe-atlas-probe-sof… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: Surrounded by the Clouds - A Comprehensive Cloud Reachability Study
by Alun Davies 12 May '21

12 May '21

Dear colleagues, Lorenzo Corneo and colleagues recently conducted a comprehensive cloud reachability study to evaluate the suitability of modern cloud environments for latency-sensitive applications. Read about the results of the study now on RIPE Labs: https://labs.ripe.net/author/lorenzo-corneo/surrounded-by-the-clouds-a-comp… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Result delivery issues - 2021-05-11
by Robert Kisteleki 11 May '21

11 May '21

Dear All, The RIPE Atlas result storage backend started experiencing issues today at around 3am (CEST). The team is working on resolving the issue; we'll provide an update when more information is available. The result streaming feature is not affected, it is still delivering results in real-time. Regards, Robert Kisteleki

2 2

Scheduler adding extra probes for some measurements
by Chris Amin 07 May '21

07 May '21

Dear colleagues, We have fixed a bug in the RIPE Atlas scheduler which caused extra probes to be added to some ongoing measurements. This bug affected many users who submitted "removal" requests using the REST API from 2021-03-23, and in some cases caused a large increase in the consumption of credits due to the extra generated measurement results. This bug has now been fixed, and the affected accounts have been credited with approximately 125% of the erroneous overpayment. My apologies for any inconvenience caused. Please let me know if you have any further questions or issues. Kind regards, Chris Amin RIPE NCC

1 0

Rapidly decreasing credits
by ms 07 May '21

07 May '21

Hi, Recently, looks like since beginning of April, my credits started dropping exponentially. I'm only running a ping measurement at the moment. Any changes to the credit system I missed? Cheers, ms

2 1

research support: credits/limits for DSCP marking measurements
by Stephen Strowes 07 May '21

07 May '21

Hi, One more RIPE Atlas research support request: this time on DSCP marking/bleaching from as many vantage points as possible. This one feeds into the IETF tsvwg, and is pretty applicable to operators in the RIPE community also. In short: they have one target host, and they want to test 3 DSCP codepoints with traceroutes from as many probes as possible. This is not an ongoing study. They'll run a pretty typical traceroute config from as many probes as possible once for each DSCP they're interested in, and they'd like to do it as rapidly as possible. This is simplest as three one-off measurements. Could you: - bump their credit allowance if necessary - bump the number of probes allowed per measurement to some high number; as close to "all probes" as possible? The account they're using is ana(a)erg.abdn.ac.uk <mailto:ana@erg.abdn.ac.uk> Cheers, S. -------- Forwarded Message -------- Subject: Re: Can you help perform a large-scale ATLAS measurement campaign? Date: Tue, 4 May 2021 19:48:40 +0100 From: ana(a)netstat.org.uk To: Stephen Strowes <sds(a)ripe.net> Hi Stephen, > Would you like to run (e.g.) thousands of probes to the target with > all DSCP values as rapidly as possible, or would you run multiple > measurements with 1,000 probes each over a longer period? > Thousands of probes as rapidly as possible, but each DSCP is a separate measurement (so 3 separate measurements). I don’t expect to repeat them over a longer period. > > Either way, the credit cost will likely be the same, but the Atlas > folks may need to modify other limits to accommodate the measurements. > Your current account settings should be visible at > https://atlas.ripe.net/atlas/user/ > The only limit that worries me there is: Maximum number of probes per measurement:1,000 It doesn’t look like these measurements will hit the other limits. > Also: Is this email address the one to add credits to? > The account uses email address ana(a)erg.abdn.ac.uk <mailto:ana@erg.abdn.ac.uk>, rather than this one. Thanks again! Ana

3 3