December 2020 - 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

Request for credits for research
by Mohan, Nitinder 20 Apr '21

20 Apr '21

Dear RIPE community, I hope you are all safe and sound. I am a Postdoctoral fellow at the Technical University of Munich, Germany. We are currently working on an ongoing research project which aims to analyze the availability and reachability of cloud data centers globally. The first work of our work will appear in ACM HotNets 2020 titled "Pruning Edge Research with Latency Shears" (http://conferences.sigcomm.org/hotnets/2020/program.html). We are currently preparing the camera-ready version of the paper and will share it with the community by hosting it (and the associated dataset) publicly soon. We are currently planing to submit the second leg of our work to a conference with submission deadline a month. In order to complete all set of measurements for required analysis, we are scheduling very large-scale measurements over the platform which has burned through almost all our credits and left us in need. I have always found the RIPE Atlas community to be helpful and generous towards research and I am hoping that you could support our research by donating us some of your spare credits. Your help will be highly appreciated. My RIPE account is nitinder.mohan(a)helsinki.fi Thanks and Regards Nitinder Mohan Postdoctoral Fellow Technical University of Munich, Germany <http://www.cs.helsinki.fi/u/nmohan/>https://www.nitindermohan.com/

15 18

Anyone else getting high requests for hitlist-rr6.hitlist.sdstrowes.co.uk
by Anurag Bhatia 28 Dec '20

28 Dec '20

Hello everyone, There seems to be high regular request on my for hitlist-rr6.hitlist.sdstrowes.co.uk. Anyone else getting the same? Since the DNS fails and it gives SERVFAIL, wondering why it's going on from over a day now. Thanks. -- Anurag Bhatia anuragbhatia.com

4 5

new website, but outdated information
by Thomas Schäfer 15 Dec '20

15 Dec '20

Hi, https://atlas.ripe.net/resources/announcements/ (Technical Updates) the last version mentioned there is: 4965 Now we are at 5020. same here: https://atlas.ripe.net/resources/source-code/ (except the link to github, that's up to date) https://atlas.ripe.net/resources/code/ Contributed Code on GitHub (https://atlas.ripe.net/github ) link is dead. Regards, Thomas

2 1

Probes suffering DNS interception?
by Ray Bellis 15 Dec '20

15 Dec '20

Is there any RIPE policy about whether nodes that are subject to DNS interception should be excluded from results (or maybe even dropped altogether) ? While these probes are perhaps still useful for ping and traceroute tests, they are effectively useless for DNS related tests other than as a proxy measure for how prevalent that practise actually is. For the visualisation I've just been building based on the Root System's "hostname.bind" data returned by Atlas it was pretty difficult to figure out how to exclude those probes on the client side. If there was a heuristic that could be applied on the probe itself or within the RIPE data collector that tagged the probe as having "bad DNS" that would help a lot. cheers, Ray Bellis Director of DNS Operations, ISC.

10 11

Re: [atlas] Probe operator notifications
by ripe＠brite.cz 13 Dec '20

13 Dec '20

For this purpose I use an online ping check service. Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside. To be exact, I use http://wedos.online that is run by one of the largest server-hosting company in the Czech Republic. It is free of charge. You can choose how often (1 minute or more) it will ping the probe and how many pings can be lost, then it sends both DOWN and UP notifications (email, Slack, Rocket chat) Cheers Jiri ______________________________________________________________ > Od: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> > Komu: "Edward Lewis" <edlewisjr(a)cox.net>, "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> > Datum: 11.12.2020 12:16 > Předmět: Re: [atlas] Probe operator notifications > >+1 for 'your probe came back on-line' > >Regards, >Grzegorz > >From: Edward Lewis <edlewisjr(a)cox.net> >Date: Thursday 2020-12-10 at 22:32 >To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> >Cc: Ed Lewis <edlewisjr(a)cox.net> >Subject: [atlas] Probe operator notifications > >(Seeing the thread about DNS intercepted probes reminded me to send this:) > >For 5 or so years running I have a probe operating in my garage (behind my home’s NAT and using the ISP’s NXDOMAIN rewriting, non-DNSSEC handling recursive server) a run-of-the-mill home cable set up. > >When I got my November report, it said I’d been down the last half of November. That was news to me. I then down'd/up’d it and it reconnected and seems to be on-line again. > >I do get the “your probe went off-line” notices. I would like “your probe came back on-line” notices as well. If we had those, I may have noticed it stayed down after the last message I saw. > >Ed > > > > > >

5 4

Credit request
by Konstantin Averkin 04 Dec '20

04 Dec '20

Good afternoon, My name is Konstantin Averkin, and I am a Bachelor student of University of Twente. Currently, I am working on my thesis on resilience of DNS servers. In order to successfully perform the research, I need to do ping and trace route measurements against a series of DNS servers located all around the world. With this email I am writing to ask you to provide 20 million credits to perform measurements with the RIPE Atlas platform. Would that be possible? My account is linked to the same name and address as in this email. Thank you in advance. Kind regards, Konstantin Averkin

8 10