March 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

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

What to do with broken v1 probe?
by Lorenzo Colitti 30 Mar '21

30 Mar '21

Fellow atlas users, After more than 10 years (!) of 99% uptime (see below), my probe v1 appears to have given up the ghost. When connected to power, the lights still come on, but after a few seconds link bounces, and it never sends any packets. Any idea what to do? Should I just apply for a new probe? Are new probes being given out these days? Cheers, Lorenzo ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Tue, Nov 24, 2020 at 9:59 PM Subject: Congratulations! Your RIPE Atlas probe 333 is 10 years old! To: Lorenzo Colitti <lorenzo(a)colitti.com> Dear Lorenzo Colitti, It's your probe's birthday today !! To celebrate that fact, we are giving you 9869024 credits to use for scheduling your own measurements. In the last 10 years your probe was connected for 99% of the time. Happy measuring and thank you on behalf of everyone at the RIPE NCC and the other RIPE Atlas users. The RIPE Atlas Team

7 6

Re: [atlas] Probe location obfuscation
by Ponikierski, Grzegorz 26 Mar '21

26 Mar '21

I would add to it additional problem that some hosts obfuscate probe location even more. For example you can find probes which in reality are located in US but are marked as CN or probes which are in reality in Wisconsin but are marked in California. Of course these are extreme cases. I guess most hosts just put a pin with probe location just somewhere around where it's locate as long it's in the same city. I don't remember, as a host of 3 probes, to get any precise recommendations how to mark probe location. Personally I just put a pin in city district where probe is locate. Regards, Grzegorz From: "Mccherry, Paul (Student)" <p.mccherry(a)lancaster.ac.uk> Date: Thursday 2021-03-25 at 11:20 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Probe location obfuscation Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public<https://urldefense.com/v3/__https:/atlas.ripe.net/about/faq/*are-the-locati…> I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

10 13

Unused Probes (was: What to do with broken v1 probe?)
by Sylvain Baya 25 Mar '21

25 Mar '21

{change the subject [0]} Dear all, Hope you are doing well! Le lun. 22 mars 2021 10:35, Estelmann, Christian <c.estelmann(a)gmx.net> a écrit : > Is there a possibility to return no longer used probes? Hi Christian, Thanks for your email brother. ...imho, it's a very useful idea! Within one [1] of our NOG's activities we have included the recovery of unused probes ; but maybe we should have tried it the other side...by asking probe's hosters to send it to an other volunteer or to us, if they become unable to keep it online... __ [1]: FR <https://www.cmnog.cm/dokuwiki/IdeasAndProjects:Projects:AtlasCM> I have one which was homed at a now closed location. Someone else could > give it a new home. > ...i suggest that you write to your ccNOG's mailinglist to find the nearest volunteer who could want to host your protected probe ;-) ...hope this could help. Blessed thursday! __ [0]: <https://lists.ripe.net/pipermail/ripe-atlas/2021-March/004638.html> Shalom --sb. > Greeting, > Christian > > Am 21. März 2021 17:14:57 MEZ schrieb Chriztoffer Hansen <ch(a)ntrv.dk>: > >On Sun, 21 Mar 2021 at 08:18, Lorenzo Colitti via ripe-atlas wrote: > >> After more than 10 years (!) of 99% uptime (see below), my probe v1 > >appears to have given up the ghost. [...] > >Cheers, > >Chriztoffer > > -- -- Best Regards ! __ baya.sylvain[AT cmNOG DOT cm]|<www.cmnog.cm/dokuwiki> Subscribe to Mailing List: <lists.cmnog.cm/mailman/listinfo/cmnog/> __ #‎LASAINTEBIBLE‬|#‎Romains15‬:33«Que LE ‪#‎DIEU‬ de ‪#‎Paix‬ soit avec vous tous! ‪#‎Amen‬!» ‪#‎MaPrière‬ est que tu naisses de nouveau. #Chrétiennement‬ «Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)

1 0

Probe location obfuscation
by Mccherry, Paul (Student) 25 Mar '21

25 Mar '21

Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

1 0

Probe #1000165 showed as down in tab#status
by Jacques Lavignotte 02 Mar '21

02 Mar '21

Dear RIPE NCC crew, Some diag below : # systemctl status atlas mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Do a controller INIT mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Controller init -p 443 atlas(a)ctr-fsn01.atlas.ripe.net INIT mars 02 11:12:43 melusine.eu.org ATLAS[32011]: 255 controller INIT exit with error Probe seems down since scheduled machine reboot this night. Help for fixing welcome, Merci, Jacques -- GnuPg : 156520BBC8F5B1E3 Because privacy matters. « Quand est-ce qu'on mange ? » AD (c) (tm)

5 6