- ripe-atlas - mailman.ripe.net

Data in the Internet Maps
by Davey Song(宋林健) 21 Dec '18

21 Dec '18

Hi Atlas people, <I did not receive mails from this list months ago. I hope it still works.> I’m writing to ask about the Data repo in the intnernet maps. For example I would like to study the DNS root RTT statistics in this page : https://atlas.ripe.net/results/maps/rtt-fixed/ Where and How should I get the access to this data. Best regards, Davey

3 6

testing DNS flag day compatibility
by Petr Špaček 19 Dec '18

19 Dec '18

Hello everyone, this is follow-up from RIPE 77 hallway discussion, sorry for delay. We are looking for ways to test DNS flag day [1] compatibility from client networks. Objective is to test hypothesis that most breakage happens on authoritative side of DNS. In other words, we would like to test that DNS recursive infrastructure and client networks do not significantly influence compatibility. That would help to provide precise information for network operators who will have to deal with DNS flag day. Problem here is that RIPE Atlas does not allow to send all types of queries [2] required for full test. It was discussed at length that Atlas team has its reasons for not sending random blobs to random IP addresses, which is understood. Question here is: Can we find a middle ground to allow greater variety of valid DNS queries without forcing Atlas team to reimplement everything? My notes from meeting mention two approaches for further dicussion: a) User provides command line arguments for well-known tool dig, which gets executed in controlled environment ("as part of RIPE Atlas infrastructure") and generates query packet/blob. This blob generated by dig is then used as payload so use cannot ship anything but syntactically valid DNS packet. b) User provides blob for payload, which is then analyzed by packet parser of choice (BIND/ldns/Knot DNS/all of them). The payload can be sent out only if packet parsers do not find out any problem/blob is syntactically valid. These two approaches can also be combined to guard again quirks in either component. c) <propose your own here> What do you think? Is there a way to allow greater flexibility to Atlas DNS? [1] https://dnsflagday.net/ [2] https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing/blob/master/genr… -- Petr Špaček @ CZ.NIC

2 4

Long response times using one-off measurements with old probes
by Moritz Muller 17 Dec '18

17 Dec '18

Hi, I would like to point you to a discussion on the DNS-OARC mailing list: https://lists.dns-oarc.net/pipermail/dns-operations/2018-December/018196.ht… One of the operators at .ca noticed that old probes report way higher response times using DNS CHAOS queries (300% or more) (see also [3]). After some digging, we came to the conclusion that this has to do with the fact that he is carrying out “one-off” measurements. When carrying out the same query for a longer time, we cannot observe this delay. The issues seems to be that one-off measurements are scheduled at probes using a different library than measurements that run for a longer period (“eooqd” instead of “eperd”). Some small additional delays have been documented before on the RIPE Atlas website and in research papers [1, 2], but the big delay with one off measurements was new to me. Also to others? Is our assumption correct that the scheduler is the culprit? Moritz [1] https://dl.acm.org/citation.cfm?doid=2805789.2805796 [2] https://clarinet.u-strasbg.fr/~pelsser/publications/Holterbach-ripe-atlas-s… [3] https://atlas.ripe.net/measurements/18086197/#!probes

2 3

API is sluggish
by Ponikierski, Grzegorz 11 Dec '18

11 Dec '18

Hi all! Did you notice that for last few days API is super slow to response. It takes something like few minutes to get reply. Do you observe any issue with Atlas infrastructure? What details I should provide to help with troubleshoot? Regards, Grzegorz

2 3

DNS Measurement Grouping by NSID
by Klaus Darilion 30 Nov '18

30 Nov '18

Hi! IIRC, the map of the DNS measurement allowed to group the dataset by NSID. Was this feature removed? OR is it now somewhere else? I.e.: https://atlas.ripe.net/measurements/17175212/?filter=&diversity-picker=3&ag… Thanks Klaus

4 6

Minor change to Atlas anchor DNS resolver configuration
by Anand Buddhdev 28 Nov '18

28 Nov '18

Dear colleagues, Each RIPE Atlas anchor runs a DNS resolver. This resolver is configured as the primary resolver for the anchor, with the following directive at the top of the resolver configuration (/etc/resolv.conf): nameserver 127.0.0.1 For ease of configuration management, we are changing this directive to: nameserver ::1 This change will not affect DNS resolution on the anchors in any way. However, any measurement that does DNS lookups using the anchor's primary resolver will contain "::1" instead of "127.0.0.1" in "src_addr" field of results. If you're using any code to parse such results, and specifically looking for "127.0.0.1", you'll need to adjust your code to also look for "::1". Regards, Anand Buddhdev RIPE NCC

1 0

no measurements
by Teun Vink 20 Nov '18

20 Nov '18

Hi, Are there any problems with the Atlas backend? All requests are answered with {u'info': u'Something went wrong with our back-end', u'type': u'redis- fail'} I don't see any working measurements in our webportal as well. Best regards, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

2 3

New on RIPE Labs: Announcing RIPE Atlas VM Anchors
by Alun Davies 12 Nov '18

12 Nov '18

Dear colleagues, We just this morning published an article announcing that, as of today, we are accepting applications for anyone interested in hosting RIPE Atlas VM anchors. The article points you to all the information you’ll need to apply for and install a virtual anchor: https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors <https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchor-vms> Kind regards, Alun Davies RIPE NCC

5 6

Temporary problem with RIPE Atlas measurement creation
by Chris Amin 01 Nov '18

01 Nov '18

Dear RIPE Atlas users, Due to a complication during a deploy, there was a problem scheduling RIPE Atlas measurements from approximately 12:50 to 14:14 UTC. Most new measurements created during this time will not have been scheduled properly. The issue is now fixed for new measurements, so if your measurements didn't work during this time you can try to create them again and it should work. Apologies for any inconvenience caused. Regard, Chris Amin RIPE NCC

1 0

Delays over the weekend
by Robert Kisteleki 29 Oct '18

29 Oct '18

Dear all, Some of you have noticed that there were delays in how RIPE Atlas behaved, starting on Saturday. This happened because of an issue deep in the bowels of the infrastructure which caused tasks (including measurement requests) to pile up. We believe the issue has been resolved by now, though we're still investigating the root cause of the issue. We apologise for the inconvenience this caused. Regards, Robert Kisteleki RIPE Atlas team

1 0