- ripe-atlas - mailman.ripe.net

ipv6 ping to root name servers failing?
by Tapio Sokura 04 Oct '17

04 Oct '17

Hello, I noticed a few days ago from the built-in probe graphs that ipv6 pings started to fail to the a-root name server instance serving the probe I host. Now also the j-root serving the probe is dropping pings. Some other instances of the same root servers at the moment are still answering pings. If it is intentional that root name servers are starting to drop pings, something should probably be done to the built-in probe measurements/graphs. Does someone know more about this, will all roots be dropping pings in the future or is this just a Verisign thing (a and j operator)? Tapio

2 1

List of Atlas probes subjected to DNS traffic interception (MITM)
by Baptiste Jonglez 29 Sep '17

29 Sep '17

Hi, I am looking for a list of Atlas probes that suffer from DNS traffic interception, to exclude them from my measurements. What I mean by "traffic interception" is that DNS queries from the probe to a third-party DNS server do not reach the server, but are intercepted and answered by a middle-box instead. I started building this list myself, but it's a long and potentially error-prone process. It seems that the "DNS Root Instances" map could be used for that purpose, because DNS traffic interception shows up as if the probe was contacting an "Unknown" root instance. To get the list of probes, I ended up using an URL like the following, showing probes for all possible "unknown" root instance hostnames: https://atlas.ripe.net/results/maps/root-instances/?server=1&question=10300… ... However, there seems to be a limit on the size of the URL so I cannot get all probes, and they are just displayed on the map without any obvious way to get the raw list of probes instead. Is there a way to get the raw list of probes from this map? Or has anybody already done this classification work independently? I also looked for DNS-related tags on probes, but could not find anything useful. Thanks, Baptiste

4 6

New on RIPE Labs: Celebrating 10, 000 Active RIPE Atlas Probes
by Mirjam Kuehne 29 Sep '17

29 Sep '17

Dear colleagues, In August 2017, just short of seven years after RIPE Atlas was launched, the number of connected RIPE Atlas probes hit 10,000. Thank you all for making this happen! Find some more details and an overview of recent developments on RIPE Labs: https://labs.ripe.net/Members/alun_davies/celebrating-10000-active-ripe-atl… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New RIPE Labs article on RIPE Atlas v3 Anchors
by Alun Davies 29 Sep '17

29 Sep '17

Dear colleagues, In this RIPE Labs article the RIPE NCC looks into hardware specifications and logistics for the next generation of RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors Best regards, Alun Davies RIPE NCC

3 3

New on RIPE Labs: Measuring your Web Server Reachability with TCP Ping
by Mirjam Kuehne 27 Sep '17

27 Sep '17

Dear colleagues, HTTP measurements from RIPE Atlas probes are only possible towards RIPE Atlas anchors. However, when it comes to measuring the connectivity and latency of web servers on the network level, an alternative exists, which we call TCP Ping: a traceroute with special options that mimic the TCP handshake that takes place when an HTTP connection is established. In this RIPE Labs article we compare the results of large scale HTTP and TCP Ping measurements: https://labs.ripe.net/Members/wilhelm/measuring-your-web-server-reachabilit… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: PoE-ing a RIPE Atlas Probe
by Mirjam Kuehne 18 Sep '17

18 Sep '17

Dear colleagues, In this new RIPE Labs article Geert Jan de Groot explains how to "PoE" a RIPE Atlas Probe: https://labs.ripe.net/Members/geert_jan_de_groot/poe-ing-the-ripe-atlas-pro… Kind regards, Mirjam Kuhne RIPE NCC

1 0

RIPE Atlas v3 Anchor Hardware
by Alun Davies 12 Sep '17

12 Sep '17

Dear all, The RIPE NCC has chosen a new model for the RIPE Atlas v3 Anchors. The hardware we finally opted for is the PC Engines APU2. As well as being cheaper than the previous generation of anchors, this model meets the majority of requirements we laid out for the next generation of anchors. To be clear, given that there are still a couple of minor logistical details to resolve, we are still keeping applications on hold for the time being. That said, we look set to meet our September deadline to resume shipping of RIPE Atlas anchors. For more information and future updates, please read our article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas… <https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas…> Kind regards, Alun Davies Comms RIPE NCC

4 3

Can Atlas probe handle Truncated response ?
by Davey Song(宋林健) 12 Sep '17

12 Sep '17

Hi folks, I once setup a measurement of DNS UDP to see if the number of timeout increase due to large response. The answer is yes. But I wonder if the timeout is no answer after three times of retries or also includes TCP fallback. Is it true that the probe in DNS UDP measurement will not use TCP to retry even after it receives a truncated response. Best regards, Davey

3 2

IPv6 issues with ATLAS and DNSMON
by Romeo Zwart 12 Sep '17

12 Sep '17

dear all, Due to a human error on our side, there have been problems with IPv6 connectivity to/from many of our servers, including atlas anchors since approximately 9:30 UTC this morning. The problem has been corrected and systems are recovering, but you may still see some problems in RIPE Atlas and DNSMON. We're still investigating the full impact of the problem and will have more information at a later stage. We apologise for any inconvenience. Romeo Zwart

1 1

Infrastructure upgrades
by Robert Kisteleki 06 Sep '17

06 Sep '17

Dear all, Yesterday we began infrastructure (OS) upgrades on our controllers. As a consequence each probe will be disconnected for an hour or two. This can trigger notifications, if you have that configured to a sensitive enough setting. Regards, Robert Kisteleki RIPE NCC

3 4