September 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

Planned changes to "measurement archive"
by Robert Kisteleki 12 Nov '20

12 Nov '20

Dear RIPE Atlas users, You may be aware that we publish "measurement metadata dumps" on "FTP" (https://ftp.ripe.net/ripe/atlas/measurements/) every week. These are meant to make the complete measurement metadata downloadable for those who are interested. Even though there is still a point in publishing our metadata in a downloadable format, the current method is not sustainable: as it is defined it'll grow forever - which is not realistic. Currently *every* dump contains *all* the measurements we *ever* had in the system. We plan to change that to "everything that's running now + everything that was running in the last two weeks". This has about 200k items currently. If we published this every day instead of once a week, we will still only produce 10% of the output we do today - by virtue of eliminating 90% of redundancy and repeated work. The syntax and semantics of the content will not change. We will keep the existing dumps as they are mostly because there's no reason to remove them. What this means for users is: * if you care about "current / recent" measurements, you can just use the last dump from yesterday * if you really need all (or a large part of) history, you can fetch one dump per 2 weeks or so and combine them * you can still use the API for random, finite searches We plan to implement the above change just after RIPE 81 (i.e. early November). Please be aware of this change if you rely on these dumps. Regards, Robert

1 1

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

Re: [atlas] ripe-atlas Digest, Vol 109, Issue 11
by Florian Rohde 24 Sep '20

24 Sep '20

10 million points have just been added to the Research Concern. I wish you success. Cheers, Florian Florian Rohde Neue Landbuch GmbH & Co. KG Telefon: +49 4231 9552-79 Fax: E-Mail: Florian.Rohde(a)nlb.de --------------------------------------------------------------------------------- Neue Landbuch Gesellschaft m.b.H Gesellschaft für moderne Datenverarbeitung & Co. KG Heinrich-Schröder-Weg 1 27283 Verden Telefon: +49 4231 9552-0 Fax: +49 4231 9552-66 E-Mail: info(a)nlb.de Internet: www.nlb.de Kommanditgesellschaft mit Sitz in Verden Registergericht Walsrode, HRA 121111 Pers. haftender Gesellschafter: Neue Landbuch GmbH, Verden Geschäftsführer: Bernhard Kramer Aufsichtsratsvorsitzender: RA StB Ralf Stephany -----Ursprüngliche Nachricht----- Von: ripe-atlas [mailto:ripe-atlas-bounces@ripe.net] Im Auftrag von ripe-atlas-request(a)ripe.net Gesendet: Donnerstag, 24. September 2020 12:00 An: ripe-atlas(a)ripe.net Betreff: ripe-atlas Digest, Vol 109, Issue 11 Send ripe-atlas mailing list submissions to ripe-atlas(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.ripe.net/mailman/listinfo/ripe-atlas or, via email, send a message with subject or body 'help' to ripe-atlas-request(a)ripe.net You can reach the person managing the list at ripe-atlas-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ripe-atlas digest..." Today's Topics: 1. Re: Request for credits for research (Ponikierski, Grzegorz) ---------------------------------------------------------------------- Message: 1 Date: Thu, 24 Sep 2020 09:46:45 +0000 From: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> To: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi>, "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] Request for credits for research Message-ID: <EEB33D82-5DC6-481B-89B0-C11B6FB52EC6(a)akamai.com> Content-Type: text/plain; charset="utf-8" 50M from me. Waiting for paper ;) Regards, Grzegorz From: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday 2020-09-24 at 00:02 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Request for credits for research 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__conferences.sigcomm.org…>). 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 https://www.nitindermohan.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nitindermohan.com_…>

1 0

Re: [atlas] Request for credits for research
by Ponikierski, Grzegorz 24 Sep '20

24 Sep '20

50M from me. Waiting for paper ;) Regards, Grzegorz From: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday 2020-09-24 at 00:02 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Request for credits for research 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__conferences.sigcomm.org…>). 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 https://www.nitindermohan.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nitindermohan.com_…>

1 0

Invalid results in TraceMON tool
by Andreas Siskos 09 Sep '20

09 Sep '20

Hello everyone, I am an undergraduate student at University of Crete and as a part of my bachelor thesis, I am trying to integrate TraceMON in a website. I used the example code that it was provided by the web page of TraceMON in RIPE Atlas website ( https://atlas.ripe.net/docs/tools-tracemon/#embed) but I noticed something unexpected. The graph of the TraceMON was not taking the same path as the raw data of traceroutes. There were the right destinations/IPs, but in shuffled order. Let's consider the example of measurement ID 26813196. As you can see, in the raw data of the traceroute ( https://atlas.ripe.net/api/v2/measurements/26813196/results/) it reaches the target IP (103.83.160.1) at 16th hop from probe 55564. When I checked the graph in TraceMON on the RIPE Atlas website ( https://atlas.ripe.net/measurements/26813196/#!tracemon) (see attached: general.png), the traceroute from probe 55564 was represented in the picture graph.png. As you can see in the data file data.png, the destination IP was reached at 3rd hop instead of 16th, that was in the raw data of the traceroute. The same behavior can be observed for the probes 19648 and 32788. Am I missing something? Thank you in advance, Andreas Siskos

1 0

How can I reduce data usage on remote satellite-connected islands?
by chris＠gare.co.uk 09 Sep '20

09 Sep '20

Hello all, I've just become an ambassador for the RIPE Atlas programme. I have a question. I wish to deploy a number of probes to remote low-capacity satellite connected islands. These islands have strict and VERY expensive monthly usage quotas. Looking at some probes already installed, I see that the minimum bandwidth (is that the term used?) is approximately 3.3kbit/s This equates to around 1GB of data per month which represent a significant percentage of a consumer's monthly quota. I'll have a hard job convincing volunteers to act as hosts if they consume that much. Is there a way I can set 'bandwidth' to less than 10kbs or is there a workaround I can use to reduce this under my control? It has been suggested that I could out a timer on the host but that is nonworkable! Any help would be appreciated as I know that reachability is quite unreliable at times and the data I could provide would be most interesting. Chris

1 0

Extreme slowness today?
by Stephane Bortzmeyer 04 Sep '20

04 Sep '20

23 minutes before Atlas tells me there is no suitable probes with my criteria (country=SD, which does not surprise me). Same slowness for all measurements.

1 0

Software vs Hardware probes
by Marty Strong 03 Sep '20

03 Sep '20

Posting to the list hoping somebody has already found the answer :) Is there a way to filter by probe architecture, or perhaps software vs hardware probes? Marty

2 1

RIPE Atlas usage webinar (and software probe installation demo)
by Lia Hestina 02 Sep '20

02 Sep '20

Dear all, The RIPE NCC will host a two day RIPE Atlas webinar with two RIPE Atlas ambassadors as guest trainers, Anurag Bhatia and Swapneel Patnekar. If you are interested in learning to use RIPE Atlas for network monitoring and troubleshooting, and also learning how to install a RIPE Atlas software probe, please join us tomorrow. More information is available here: https://atlas.ripe.net/resources/training-and-materials/innog-webinar/ <https://atlas.ripe.net/resources/training-and-materials/innog-webinar/> If you would like to participate, please send an email to e-learning(a)ripe.net <mailto:e-learning@ripe.net>. Thank you, Lia Hestina

7 11

RIPE Atlas virtual events @ Rootconf
by Lia Hestina 02 Sep '20

02 Sep '20

Dear all, Rootconf organises RIPE Atlas related events starting next week. You will find the information of each event and how to register in the link below: Talk by Philip Paeps: https://hasgeek.com/rootconf/monitoring-internet-networks-using-ripe-atlas-… <https://hasgeek.com/rootconf/monitoring-internet-networks-using-ripe-atlas-…> Workshop by Swapneel Patnekar: https://hasgeek.com/rootconf/measuring-the-internet-using-ripe-atlas/ <https://hasgeek.com/rootconf/measuring-the-internet-using-ripe-atlas/> - Feel free to share this information with friends and colleagues who may be interested in joining and learning more about the RIPE Atlas. Kind regards, RIPE Atlas team _________

2 2

Disabling TLS 1.0 and 1.1 on RIPE Atlas anchors
by Robert Kisteleki 01 Sep '20

01 Sep '20

Dear RIPE Atlas users, We received reports that the availability of TLS 1.0 and 1.1 on RIPE Atlas anchors triggers some security alarms for some anchor hosts. Since the anchors don't host anything sensitive, and the measurment code is not expected to be affected by this, we will stop supporting these protocols on the anchors (*) as of *1 September*. We'll carry on with supporting TLS 1.2 (*) the RIPE Atlas website/UI will be unchanged for the time being although we expect similar changes in the near future Regards, Robert Kisteleki RIPE NCC

3 5