May 2019 - ripe-atlas - mailman.ripe.net

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

Feature Request to consider: DNS response IP header
by Jen Linkova 22 Jul '19

22 Jul '19

Hello, I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements. So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it? Thanks! -- SY, Jen Linkova aka Furry

4 4

RFC1918 probes
by Mayer Hans 22 May '19

22 May '19

Dear All, Looking at the result of a traceroute measurement I see very often that first hop has a RFC1918 address. These days a found a result where the first 3 hops are showing something like 192.168.x.y Of course this could falsify the result especially for response time. Is there a way to select only Atlas probes which are located in non RFC1918 networks ? If not it would be nice to have such a possibility. Kind regards Hans -- Ing. Dipl.-Ing. Hans Mayer Systems Administrator Information and Communication Technologies (ICT) International Institute for Applied Systems Analysis (IIASA) Schlossplatz 1 A-2361 Laxenburg, Austria Phone: +43 2236 807 Ext 215 Mobile: +43 676 83 807 215 Web: http://www.iiasa.at E-Mail: mayer(a)iiasa.ac.at Atlas probe: 35603 Note: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it.

3 5

New probe tags proposal
by Antonios Chariton 18 May '19

18 May '19

Hello everyone, I believe it would be of interest to have system-assigned tags to probes based on whether their network is performing RPKI validation or not. This can be two new tags, “rpki-validating” and “no-rpki-validation”, or similar. The tags should be assigned per probe, using RIPE’s RIS Routing Beacons [1], by running system ping checks every hour / day. What do you think? Would this be something that you would find useful? Thanks, Antonis 1: https://www.ripe.net/analyse/internet-measurements/routing-information-serv… <https://www.ripe.net/analyse/internet-measurements/routing-information-serv…>

2 1

Re: [atlas] [WARNING! RECEIVED FROM EXTERNAL SENDER] Incorrect location of probe #6422
by Ponikierski, Grzegorz 09 May '19

09 May '19

BTW it's an anchor. I guess that location of anchors should be double-checked as they play important role. Regards, Grzegorz From: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> Date: Tuesday 2019-05-07 at 17:37 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [WARNING! RECEIVED FROM EXTERNAL SENDER] [atlas] Incorrect location of probe #6422 Hi all! According to Atlas probe #6422 is located in Los Angeles but from measurements it's clear that probe is in Miami. Can somebody relay this information to probe owner to fix location? Regards, Grzegorz

2 1

Incorrect location of probe #6422
by Ponikierski, Grzegorz 07 May '19

07 May '19

Hi all! According to Atlas probe #6422 is located in Los Angeles but from measurements it's clear that probe is in Miami. Can somebody relay this information to probe owner to fix location? Regards, Grzegorz

1 0

Communication with probes' owners
by Ponikierski, Grzegorz 01 May '19

01 May '19

Hi all! From time to time I find probes which has incorrect country in their description. For example #10333 supposed to be in US but from my measurements it looks like it is somewhere nearby Amsterdam. If something has 10ms RTT to target in Amsterdam, has hops with `nl-ams14a-ri1-ae8-0.aorta.net<https://stat.ripe.net/nl-ams14a-ri1-ae8-0.aorta.net>` description and has ASN for LibertyGlobal then this probe is rather in Europe. It takes some time to resolve such issue via RIPE team so maybe we can get a form to send direct and short message to probe owner to let him/her know that something is wrong with his/her probe and we ask for verification. What do you think about that? Regards, Grzegorz

9 13