- ripe-atlas - mailman.ripe.net

Recent TLS supported by probes?
by Stephane Bortzmeyer 13 Nov '17

13 Nov '17

I cannot get the certificate for <https://dns-resolver.yeti.eu.org/> (measurement #10174881): "alert" is "{u'description': 40, u'level': 2}". It works with other, more "mainstream", HTTPS sites (see #10174883). I suspect this is because the probes don't handle the recent TLS stuff. Can anyone confirm or infirm?

2 1

Atlas Measurements
by Tom Glass 13 Nov '17

13 Nov '17

Hello all, Hope you are having a great weekend. I just stopped by to ask if you guys would know where/if I can add new probes to an existing measurement. A new probe has appeared in the area we are monitoring and I was hoping there was a way of adding it without recreating the measurement? Cheers, all, Tom

2 1

Odd queries from probe
by Jared Mauch 10 Nov '17

10 Nov '17

While doing some debugging of my home network, I noticed some odd queries from the probe, namely this one: 02:28:36.921622 IP6 fe80::a2f3:c1ff:fec4:479f.51123 > 2001:558:feed::2.53: 23808+ A? 12920.atlas.ripe.net.b61065696c194ac3. (55) Is this some captive portal/wildcarding detection, or perhaps some other software issue? curious, - Jared

2 1

IPv4 leading zeroes and weird interface behaviour
by Max Grobecker 30 Oct '17

30 Oct '17

Hello, is there - by standard - a definition on how to represent an IPv4 address? I have (for example) the IP address "73.0.255.229", which can IMHO also be written as "073.000.255.229" as the leading zeroes are not giving any changes to the binary representation of this address. Am I right on this? But: When I lookup this IP address on https://stat.ripe.net/073.000.255.229 the first octet is internally getting swapped to "59". This can be explained, if you take "073" as an octal value and convert it to a decimal value. It is definitely a octal-to-decimal conversion thing, as for example also the value "010" is getting replaced by "8" and so on. Now I'm puzzled: Of course, writing IPv4 octets with leading zeroes is not very common. But: Is it officially prohibited or discouraged? This weird conversion also happens inside the "geoiplookup" tool by MaxMind and I'm not sure if I'm going to be the moron in this story or if I found the same bug inside multiple softwares at once ;-) Thanks and greetings from Wuppertal Max

8 7

Segmentation fault (core dumped)
by Antonio D 26 Oct '17

26 Oct '17

I upgraded UBUNTU from 17.04 to 17.10 and I discovered that ripe-atlas-tools had disappeared. So I tried reinstalling it with "pop install ripe-atlas-tools", but the process crashed with the following error: Segmentation fault (core dumped) Can you help me solve the problem? Thank you Antonio Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

Why did I get "Over the limit on number of results"?
by Eduardo Duarte 25 Oct '17

25 Oct '17

Hello, I schedule some measurements to run during today but I got an error on some of them. The error is "Over the limit on number of results". I have enough credits to run all the measures so I don't understand this message. Thank you and best regards, -- Eduardo Duarte Gestão e Desenvolvimento de Projetos l Project Development Management *DNS.PT* Rua Latino Coelho, n.º 13, 5.º piso | 1050-132 Lisboa | Portugal Tel: (+351) 211 308 200 Fax: (+351) 211 312 720 dns.pt <http://www.dns.pt> | dnssec.pt <http://www.dnssec.pt> | 3em1.pt <https://www.3em1.pt> | facebook.com/dns.pt <https://www.facebook.com/dns.pt> | pt.linkedin.com/in/dnspt <http://pt.linkedin.com/in/dnspt> Aviso de Confidencialidade/Disclaimer: Este e-mail foi escrito de acordo com o novo acordo ortográfico. Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail and delete it immediately. [ Antes de imprimir esta mensagem pense no ambiente. Before printing this message, think about environment ]

3 2

New on RIPE Labs: RIPE Atlas Probes as IoT Devices
by Mirjam Kuehne 20 Oct '17

20 Oct '17

Dear colleagues, As a follow-up to the presentation Robert Kisteleki gave during the IoT Roundtable Meeting in September [1], we have published a RIPE Labs article describing RIPE Atlas probes as IoT devices and some initial design decisions that we thought were important for such an infrastructure: https://labs.ripe.net/Members/kistel/ripe-atlas-probes-as-iot-devices Kind regards, Mirjam Kuhne RIPE NCC [1] https://www.ripe.net/participate/meetings/roundtable/september-2017/ripe-io…

1 0

status is confusing
by Dave 18 Oct '17

18 Oct '17

Hi, The status page of one of my probes says: I’ve been bitten a few times by misinterpreting this. Could these 2 things be put on separate lines? This does suggest the probe is up but only when you missed the red colour and didn’t get the meaning of the icon. Also, when you read the mail it may be hours later than when it was sent. So keep in mind that a receiver’s probe could be back online in the meantime. Often a mail will be checked on the mobile. The status on a small screen must be clear too. I’ll restart the probe and modem and it will work again but I would have done that on day 1 if the message was more clear. Thanks, Dave

1 0

New on RIPE Labs: Insights from RIPE Atlas Probe Disconnections
by Mirjam Kuehne 17 Oct '17

17 Oct '17

Dear colleagues, There are all kinds of reasons why RIPE Atlas probes might become disconnected. So, even though we'd like all probes to be connected all the time, disconnects can also tell us a useful story. Please find this new article by Emile Aben on RIPE Labs exploring what insights we can gain from RIPE Atlas probe disconnections: https://labs.ripe.net/Members/emileaben/insights-from-ripe-atlas-probe-disc… Kind regards, Mirjam Kuhne RIPE NCC

1 0

What is the meaning of 127.0.0.1 as probe resolver?
by Baptiste Jonglez 16 Oct '17

16 Oct '17

Hi, While looking at the result of built-in DNS measurements that use the probe resolvers, I noticed that a significant fraction of probes have "127.0.0.1" as a resolver. And the results are strange: performance is really bad, for instance measurement 30002 gives a median resolution time of 300 ms for these probes! What could be the meaning of this? It almost looks like a recursive resolver with no cache at all is running on the probes themselves. I was looking at this measurement: https://atlas.ripe.net/measurements/30002/ And here are some example probes that exhibit this "127.0.0.1" symptom: 6001, 6087, 6162, 6235, 6308. Any reasonable explanation is welcome! Thanks, Baptiste

2 2

Problem in status checks?
by Stephane Bortzmeyer 14 Oct '17

14 Oct '17

Error 500 when trying to retrieve status checks: % curl -v 'https://atlas.ripe.net/api/v2/measurements/2060427/status-check?permitted_t…' ... > GET /api/v2/measurements/2060427/status-check?permitted_total_alerts=3 HTTP/1.1 > Host: atlas.ripe.net > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 500 Internal Server Error < Server: nginx/1.10.2 < Date: Sat, 14 Oct 2017 07:09:10 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 38403 < Connection: keep-alive < Vary: Accept-Encoding, Cookie < X-Frame-Options: SAMEORIGIN < Strict-Transport-Security: max-age=15768000

2 1

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 09 Oct '17

09 Oct '17

Dear colleagues, We wanted to update the community and let you know that we plan to start work on the proposed experiment with WiFi measurements in mid-2016. As we communicated in a recent RIPE Labs article, we will work with GÉANT as a test partner to learn more about the operational effects of introducing WiFi measurements to the RIPE Atlas system, in addition to the benefits we believe this could provide for the entire RIPE Atlas community. Please see the article for more details if you are interested: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… We will continue to update you once we’ve begun work on this plan, and we welcome your comments in the meantime. Regards, Robert Kisteleki RIPE NCC

3 3

Probe disconnects
by RIPE 09 Oct '17

09 Oct '17

Hi, I have a probe ( #22583 ) at home connected via my DSL link, for IPv6 connectivity I use a Hurricane Electric ( tunnelbroker.net ) /48 tunnel. I noticed on the monthly report that my probe is showing lots of short ( 1-2 min) disconnects. But it only seems to happen when the connection address in the probe’s network tab is the IPv6 address. In that case the IPv4 Connection address is empty. If it’s showing the IPv4 the probe stays connected for days ( until the DSL link really disconnects). Is there a way to get the probe to ignore the IPv6 for connection status ? Or to mark it as disconnected when both iPv4 and IPv6 are disconnected ? Best regards, Paul van der Zwan

3 2

Charity IT Pulse :) one more sleep till Bytenight Action for Children 2017
by Colin Johnston 05 Oct '17

05 Oct '17

> > Dear all, one more sleep until ByteNight events across the UK on Friday night. > Please donate if you can electronically > > > See mydonate page linked to Byte Night https://mydonate.bt.com/fundraisers/colinjohnston1 <https://mydonate.bt.com/fundraisers/colinjohnston1> > > For more information go to www.bytenight.org.uk <http://www.bytenight.org.uk/> or to donate Text Byte17 and the amount to 70070. > > In just 1 days time, on Friday 6 October, I am spending one night sleeping rough for Byte Night. Byte Night works to support some of the 83,000 young people who are homeless in the UK. One in four young people who are homeless have been diagnosed with mental health issues and one in five will have self-harmed due to their situation at home. £10 could provide an hour’s support with a mental health practitioner for 1 young people to help them get through their issues. Action for Children has supported many young people to a safe and happy future. Unfortunately, so many more still need our help. You can help support young people across the UK by generously donating to my page > > > > Yours > > Colin Johnston > > Colin Johnston <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> > IT Support Senior Professional, Core IT Infrastructure > BT Technology Service & Operations <https://intra.bt.com/bt/tso/Pages/index.aspx> | Tel: 01313001324 <tel:01313001324> | MyProfile <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> | colin.johnstone(a)bt.com <mailto:colin.johnstone@bt.com> | http://fixit.bt.com/ <http://fixit.bt.com/> > > BT Group plc Registered office: 81 Newgate Street London EC1A 7AJ. Registered in England and Wales no. 4190816 This electronic message contains information from BT Group plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please delete it and notify me immediately by telephone or email.

1 0

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

Is there a problem with ctr-ams07 right now?
by Max Mühlbronner 06 Sep '17

06 Sep '17

Hi, my probe is online (ping) and it shows SOS messages (reboots - This probe probably last rebooted on 2017-07-06 12:23:08) on the probe page. Disconnected since 59 minutes. Is this a general problem, e.g. of the controller or is it just my probe? Does someone see similar problems right now? BR Max M.

3 3