- ripe-atlas - mailman.ripe.net

DNS and recursion
by Stephane Bortzmeyer 27 May '17

27 May '17

API v1 had a field recursion_desired when performing DNS measurements. If I remember correctly (but I cannot find the reference right now), it worked only when querying a specific name server, and not when using the probe's own resolver, to avoid cache snooping. API v2 has instead a set_rd_bit. Documentation <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li…> does not indicate its default value. Anyway, my experience with the API is that the RD (Recursion Desired) bit is always set, whether with 'set_rd_bit': False or with 'set_rd_bit': True, and independant of use_probe_resolver. I can understand this choice for privacy reasons (RFC 7626, section 2.3). But, in that case, the documentation should be fixed. Anything I missed? (Here, a request by a probe, the + after the Query ID - here, 52379 - means the RD bit is set 12:22:23.170304 IP (tos 0x0, ttl 64, id 2287, offset 0, flags [DF], proto UDP (17), length 65) 192.168.2.8.45955 > 212.27.40.240.53: [udp sum ok] 52379+ AAAA? uucp.bortzmeyer.org. (37)

2 2

DNS measurement
by Stanish Stanishev 25 May '17

25 May '17

Hello, I am having troubles running a a DNS measurement against our DNS cache servers. I get Error: Timeout: 5000 every time I run such measurement. Please see measurement ID #8771668 for example. In this measurement I've selected the two anchors (ids 6262 and 6263) hosted by us (Vivacom) as the source and the target is one of our DNS cache servers - 212.39.90.42. There is no firewalls or other preventing our anchors from reaching the 212.39.90.42 and also the DNS cache server running on 212.39.90.42 is configured to serve queries from Anchors' IPs. What am I doing wrong ? Thanks, Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

RIPE Atlas V1 Probe Issue
by Alun Davies 18 May '17

18 May '17

Hello all, Due to an unfortunate bug in a recently released probe firmware (version 4760), a number of RIPE Atlas V1 probes are not currently able to connect to the network. The bug leads to excessive memory fragmentation which impacts that V1 probes because they have no MMU and only 8 MByte worth of memory. For reasons that are not yet clear, the issue has only affected well below half of the V1 probes. We are working on a new firmware that will correct this issue, but probes that will not connect will need to be returned to the RIPE NCC in order for the fix to be carried out. Once the new firmware is ready, users can either return their V1 probes to us to be fixed, or request a V3 probe instead. Thank you to Wilfred Woeber for reporting this and requesting an update on the current issue with the V1 probes. Cheers, Alun Davies RIPE NCC

4 4

Introducing blitzortung.org Network for Lightning and Thunderstorms in Real Time
by Jean-Michel Pouré 13 May '17

13 May '17

Dear Friends from RIPE community, This is my first post on the forum. I would like to point out to the community the existence of a free community providing a network device for Lightning and Thunderstorms in Real Time: http://blitzortung.org The device works the same as a RIPE probe, except that it collects information about lightning via radio and delivers the information to a central network of computers for data processing. If you are network specialist hosting very expensive network devices, it might be interesting for you to participate in the effort to build a free community and host a Blitzordnung device in your premisses. All information can be found on http://blitzortung.org and BlitzOrdnung forum : http://en.blitzortung.org/forum.php BlitzOrdnung coverage is good in Europe and North America, but BlitzOrdnung needs more devices in Africa/South America/China and Russia. All help is welcome and may save you a lot of money in lightning protection. Kind regards, Kellogs

1 0

Results of the DNS Measurements hackathon - article now published on RIPE Labs
by Vesna Manojlovic 11 May '17

11 May '17

Dear all, in April we held a fifth hackathon. Altho the topic was DNS, most of the projects were using RIPE Atlas data. Therefore, I invite you to check out the hackathon results, follow the links to the code, and enjoy the photos that attempt to transfer some of the atmosphere.. https://labs.ripe.net/Members/becha/results-dns-measurements-hackathon Please do take part: - use the tools/SW and let us know your experiences with it - modify the code & publish it again on GitHub - join our next hackathon - as a host, sponsor, or participant (date & location & topic to be announced soon!) Let me know in person if you are interested; and otherwise, post your comments or questions on the list, greetings from RIPE74, Vesna

1 0

Many timeout-failures for DNS over TCP
by Davey Song(宋林健) 11 May '17

11 May '17

Hi folks, I setup measurements for DNS queries over both TCP and UDP. I found the timeout and failures of TCP is far more than UDP. For example : DNS over TCP: https://atlas.ripe.net/measurements/8552847/#!probes DNS over UDP: https://atlas.ripe.net/measurements/8552846/#!probes Is it normal ? I mean is there any special timeout routine/parameters of atlas probes from normal resolver? Best regards, Davey

4 4

TraceMON follow up
by Massimo Candela 10 May '17

10 May '17

As a follow up to my talk at RIPE74 about TraceMON, here a link with some live examples: https://massimo.ripe.net/tracemon/widget/ <https://massimo.ripe.net/tracemon/widget/> Ciao, Massimo

1 0

Are there plans for faster than 1G anchors?
by Bryan Socha 20 Apr '17

20 Apr '17

We're finding it harder and harder to support the 1G nic interface on the anchors. We'd love to add more but would need a 10g port at minimum (25G or 40G would also work). Are there any plans to update them for networks that can't easily support a 1G nic? Bryan Socha Network Engineer DigitalOcean

4 4

status-check misbehaving
by Georg Kahest 19 Apr '17

19 Apr '17

Hello, Am I misunderstanding something or the status-checks are kind of broken: Yesterday i made new measurement: https://atlas.ripe.net/measurements/8038852/ I noticed some probes werent reaching my ipv6 host, so decided to remove them like you can see from the Probe specifications section. Now when i goto https://atlas.ripe.net/api/v2/measurements/8038852/status-check/ I can still see the removed probes in status-check page (which contains 17 errors ) in reality if i'm lookin at measurement probe page i should have only two errors. So it seems that status-check isnt updated once probes are removed from a measurement. -- Georg Kahest System Administrator / Süsteemiadministraator Eesti Interneti SA Paldiski mnt 80, 10617 Tallinn Tel 727 1016 www.internet.ee

2 1

Behind the scenes changes to measurement creation
by Chris Amin 18 Apr '17

18 Apr '17

Dear colleagues, Today we deployed behind-the-scenes changes to the measurement creation process, both when using the website and the REST API. These changes should not have any visible effects, with the exception of improvements to the measurement API reference[1] to make it easier to see which options belong to which measurement type. Although we've tested these changes extensively, they are significant so I am sending this mail to ask you to please let us know if you notice any problems or changes when creating measurements. Kind regards, Chris Amin RIPE NCC [1] https://atlas.ripe.net/docs/api/v2/reference/#!/api/Measurement_List_GET

2 3