- ripe-atlas - mailman.ripe.net

DNS over TCP problems?
by Stephane Bortzmeyer 21 Mar '17

21 Mar '17

[I did not test it myself.]

2 4

Trivia of the day: Atlas probes and alternative DNS roots
by Stephane Bortzmeyer 21 Mar '17

21 Mar '17

A quick test with a thousand probes seem to indicate that less than a dozen of all the probes use an alternative DNS root (or, more stricly, use a DNS resolver which is configured for an alternative root). The only alternative root used seems to be OpenNIC. Measurements #7865679 #7865870 #7865872 #7865873

1 1

Fwd: [mat-wg] Atlas: DNS TCP Errors
by John 14 Mar '17

14 Mar '17

Hello Atlas, feature request, when preforming DNS queries over TCP would it be possible for the probe to differentiate between a timeout and a TCP Reset. Currently the result just records the following when it gets a reset[1]. `error.timeout: 5000` A similar feature to record ICMP prohibited for udp queries would also be useful but likely much harder. Thanks John [1]https://atlas.ripe.net/api/v2/measurements/7859749/results?start=14888448…

3 3

Lowercase country codes in the probes database
by Marat Khalili 14 Mar '17

14 Mar '17

While using use probes database at ftp://ftp.ripe.net/ripe/atlas/probes/archive/ I noticed that 33 probes have country_code values in lower case (e.g. "ru" instead of "RU"), some in "Connected" state. When trying to distribute probes evenly among available countries it obviously affects the result. Of course, it's easy to work around once you are aware of this 'feature', but I only found the problem by chance. I wonder what's the story behind this and can this be fixed? (Web-interface doesn't seem to be affected.) -- With Best Regards, Marat Khalili

2 1

RIPE Atlas Infrastructure Maintenance (14 March)
by Paul de Weerd 13 Mar '17

13 Mar '17

Dear all, We'll carry out maintenance work on the core RIPE Atlas and RIPEstat infrastructure tomorrow (14 March 2017), approximately between 09:00 and 11:00 UTC+1. As a result, we will switch over to the reduced data set, limiting the amount of history available from the service. This affects RIPE Atlas, RIPEstat, RIS and DNSMON. We apologise for the inconvenience. Best regards, Paul de Weerd Senior Systems Engineer RIPE NCC

1 0

Surplus RIPE Atlas credits
by Michael Reutter 13 Mar '17

13 Mar '17

Hi everyone, I host a probe but at the moment I do not create measurements. As such, I have a large surplus of unused credits. Is anyone in need of credits and would like for me to transfer them? Best, Michael

1 0

Probe: Any benefits to set in DMZ?
by Martin Boissonneault 13 Mar '17

13 Mar '17

Hi! Is there any benefit to put the Probe in a home router "DMZ"? I could not find the answer in the FAQ. My setup is: 1- The Probe is directly connected to the ISP all-in-one router in it's DMZ (Bell Home Hub 3000, FTTH). 2- My personal router is directly connected to the ISP router, but connecting through PPPoE passthrough. Both routers have different ISP IPs. The ISP router is used for the Fiber SFP module, TV and phone. The Probe takes internet from the ISP router, but nothing else. Thanks, Martin Boissonneault Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

4 4

More even earth distribution of measurement probes
by Marat Khalili 10 Mar '17

10 Mar '17

I'd like to check worldwide connectivity to my site. I create a new measurement via web-interface and add, say, 300 probes, expecting them to cover most world countries. However, looking at the map <https://atlas.ripe.net/measurements/7861872/?filter=#map> I notice that most are selected from Europe: there're two dozens in Netherlands (many with same ASNs), but only two in Australia, one in Japan and nothing in Brazil. Obviously, most ATLAS probes are from Europe, and selection algorithm does not take probe density into account. Wouldn't it be nice to have the following features in web-interface and API: * even distribution of probes by country or continent based on population, area, and other user-defined weight numbers; * avoiding probes with same ASNs ? I don't know how current algorithm works, but easiest modification would be two-step process: (1) randomly select country based on specified weights; (2) randomly select probe within country, avoiding earlier selected probes or ASNs and failing if none are left available; repeat from step 1 until necessary number of probes is selected. P.S. I tried to manually request 1 probe from each country, but stumbled on unrecognised country codes, countries with no probes etc. before even trying population-weighted distribution. Without direct access to probes database nice solution can be difficult to achieve via current API, although crude one looks possible. P.P.S. I understand this option will create more load on probes in less-covered countries, but since it's possible to limit selection to specific countries anyway this is hardly a strong argument against adding this feature. -- With Best Regards, Marat Khalili

3 5

Testing DNS-over-TLS support?
by Stephane Bortzmeyer 10 Mar '17

10 Mar '17

DNS-over-TLS (RFC 7858) is important for privacy but, today, few DNS resolvers support it. It would be interesting to measure if this is changing, but the probes do not seem to be able to query their resolver with TLS over port 853. (Also, I seem to remember that old probes do not have a full TLS implementation.) It is not just a matter of encrypting the data, it's also an authentication issue (Google Public DNS was already impersonated <http://bgpmon.net/turkey-hijacking-ip-addresses-for-popular-global-dns-prov…>) So, how about adding a 'use_tls': True after 'use_probe_resolver': True?

2 2

No data in Connection & Traffic graph
by Danny Horne 09 Mar '17

09 Mar '17

Hi all, Is anyone not seeing any data on the Connection & Traffic graph in the General tab on their probe's homepage? (My probe ID 31491) Regards Danny Horne

2 1

Ripe website problems
by Danny Horne 08 Mar '17

08 Mar '17

Hi all, Anyone getting this when trying to get to access.ripe.net? Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /<https://access.ripe.net/>. Reason: Error reading from remote server

2 2

Failing probe, all lights blink
by Phillip Remaker 07 Mar '17

07 Mar '17

This is a new one for me. A V3 probe, when powered on, lights the power light, and then blinks all other lights for about a second every few seconds. Forever. I opened a case on it and was referred to the USB stick recovery process. Sigh. This is not that problem, I know how to deal with the USB stick issue. Has anyone seen this? Is there a deeper recovery trick we can use? I'm perfectly happy to attach a console to the TP-Link device. I was planning on doing it anyway to see what errors I am getting.

3 5

Probe Fulfilment
by Eduardo Duarte 06 Mar '17

06 Mar '17

Hi, I have craeted several measurements and the I always have a lower "Probe Fulfilment" rate. What does this mean? Thank you, Eduardo Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

HTTPS interception in Atlas probes
by Stephane Bortzmeyer 03 Mar '17

03 Mar '17

After this excellent talk at NDSS 17 <https://www.internetsociety.org/doc/security-impact-https-interception>, I wanted to see if there are some Atlas probes behind such an interceptor. I cannot run on all Atlas probes (maximum daily spending limit) but I've found at least one: % python cert.py --requested 500 --area North-Central --issuer www.afnic.fr 497 probes reported [<X509Name object '/C=NL/O=OCOM/OU=Security Dep/CN=amspan01.ocom.lan/emailAddress=security(a)leaseweb.com'>] : 1 occurrences [<X509Name object '/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Extended Validation CA - SHA256 - G2'>] : 496 occurrences Test #7854923 done at 2017-03-03T16:20:43Z The probe is #10035, in Amsterdam <https://atlas.ripe.net/probes/10035/#!tab-general> The cert.py program is at <https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib>

1 0

Feature request: API call in results page
by Hugo Salgado 03 Mar '17

03 Mar '17

Hi RIPE Atlas people. I wonder if it could be possible to add an option on the "measurements" webpage of a previous stopped or running measurement, to be able to see the API call that created it. Just like the "Measurement API Compatible Specification" section, when you create one. It could be available just to the user who created it... and even with API keys obscured. That will be very handy to be able to replay and exact measurement, or to have the list of probes in a ready-to-use format. Thanks a lot! Hugo Salgado

2 1

USB stick?
by Danny Horne 02 Mar '17

02 Mar '17

Hi all, I've seen in another thread mention of a USB stick. I've got an Atlas probe coming and haven't seen mention of a USB stick anywhere else, just the need for an Ethernet connection and USB power adapter. Have I missed something? Thanks for looking Regards Danny

2 1

modifications to Atlas front-end servers
by Romeo Zwart 02 Mar '17

02 Mar '17

dear Pier, Bjørn and all, We are in the process of migrating the atlas front-end machinery from apache to nginx. Despite our extensive preparations, this change has not been completely transparent, as you have noticed, and has caused some problems with the certificate chains. The problems with the CERTs have now been fixed. Apologies for this inconvenience to everyone. Please let us know if you would spot any other anomalies in the behaviour of the Atlas service. Kind regards, Romeo Zwart

1 0

SSL issue with atlas.ripe.net
by Pier Carlo Chiodi - Active Network S.p.A. 02 Mar '17

02 Mar '17

Hello, I'm facing an issue while using Atlas API. Some connections (not all) to https://atlas.ripe.net fail because of what seems to be an invalid certs chain. It looks like that an intermediate cert is missing. SSLLabs too reports something similar: https://www.ssllabs.com/ssltest/analyze.html?d=atlas.ripe.net&s=193.0.6.158 $ openssl s_client -connect atlas.ripe.net:443 -servername atlas.ripe.net CONNECTED(00000003) depth=0 C = NL, ST = Noord-Holland, L = Amsterdam, O = RIPE NCC, CN = atlas.ripe.net verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 C = NL, ST = Noord-Holland, L = Amsterdam, O = RIPE NCC, CN = atlas.ripe.net verify error:num=27:certificate not trusted verify return:1 depth=0 C = NL, ST = Noord-Holland, L = Amsterdam, O = RIPE NCC, CN = atlas.ripe.net verify error:num=21:unable to verify the first certificate verify return:1 --- Certificate chain 0 s:/C=NL/ST=Noord-Holland/L=Amsterdam/O=RIPE NCC/CN=atlas.ripe.net i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA --- Server certificate -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- subject=/C=NL/ST=Noord-Holland/L=Amsterdam/O=RIPE NCC/CN=atlas.ripe.net issuer=/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA --- ... Verify return code: 21 (unable to verify the first certificate) -- Pier Carlo Chiodi - Active Network S.p.A. via della Chimica, 18 - 01100 Viterbo Tel: +39 0761 17691 08 - Fax: +39 06 23328079

2 1

changing probes of a given measurement
by JORDI PALET MARTINEZ 01 Mar '17

01 Mar '17

Hi, Is it possible to change some of the probes of a given measurement? The issue is that I’ve a set of 10 probes for a specific measurement and it seems that 1 of them is no longer connected. Last time I’d this situation, I created a new measurement with the same probes except the failed one, but I wonder if it is possible to “modify” the actual measurement instead of creating a new one? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

Probe lights
by Alistair Mackenzie 27 Feb '17

27 Feb '17

Hi, I'm not sure if I'm missing something but there doesn't seem to be a guide on what the lights mean nor even how to read the SOS messages coming from the probe. I've tried resetting the USB drive and I can write to it with my laptop so I don't suspect this is the problem. Is there any information on how to diagnose this probe? Thanks, Alistair

2 1

CHAOS DNS queries
by Kyle Schomp 23 Feb '17

23 Feb '17

Hi all, For chaos txt queries, the only qnames that ripe atlas currently allows are: "hostname.bind", "id.server", "version.bind", "version.server". This seems like an unnecessary limitation to me as I've used chaos txt many times in the past for various dynamic records. I'm wondering what other peoples thoughts are on this restriction. Is this a problem for anyone else? Perhaps if there is enough community interest, the ripe atlas devs might decide to remove the restriction. Thanks! -kyle

1 0

250 RIPE Atlas Anchors now online!
by Michela Galante 23 Feb '17

23 Feb '17

Dear colleagues, Thanks to nineteen new RIPE Atlas Anchors being activated over the last three months, we have now reached an important milestone: 250 anchors online! Congratulations to anchor 250 hosted by Mogul Service and Support LLC in Ulaanbaatar, Mongolia and to APNIC for sponsoring it! These are the other anchors that have become active since our last announcement in November: - nl-ede-as12859, hosted by BIT in Ede, Netherlands - de-tua-as21413, hosted by envia TEL GmbH in Taucha, Germany - de-ham-as12731, hosted by IPHH Internet Port Hamburg GmbH in Hamburg, Germany (replaces older hardware) - py-slo-as27733, hosted by IXpy (sponsored by LACNIC) in San Lorenzo, Paraguay - uk-did-as786, hosted by Jisc in Didcot, United Kingdom - Two anchors hosted by Rabobank: nl-bst-as8211 in Best and nl-bxt-as8211 in Boxtel, Netherlands - nz-wlg-as9834, hosted by Trade Me in Wellington, New Zealand - lt-vno-as21412, hosted by CGATES in Vilnius, Lithuania - de-ber-as25291, hosted by SysEleven GmbH in Berlin, Germany (replaces older hardware) - us-bcb-as1312, hosted by Virginia Tech Transportation Institute in Blacksburg, United States - Two anchors hosted by Elisa Obj: fi-hel-as6667 in Helsinki and fi-tmp-as719 in Tampere, Finland - lu-ezt-as2602, hosted by Fondation RESTENA in Esch-sur-Alzette, Luxembourg (replaces older hardware) - de-kae-as8560, hosted by 1&1 Internet SE in Karlsruhe, Germany - fr-par-as5377, hosted by Marlink Enterprise AS in Paris, France - fr-tls-as39405, hosted by FULLSAVE in Toulouse, France - nl-ams-as286, hosted by KPN Eurorings B.V. in Amsterdam, Netherlands - mm-rgn-as132167, hosted by Ooredoo Myanmar (sponsored by APNIC) in Yangon, Myanmar (IPv4-only anchor) - fr-ilm-as57119, hosted by NAITWAYS in Issy, France - us-lxa-as8560, hosted by 1&1 Internet Inc. in Lenexa, United States You can find the full list of anchors, a map of their locations, a list of the hosting organisations and more information about RIPE Atlas Anchors online: https://atlas.ripe.net/anchors/list/ Interested in hosting a RIPE Atlas Anchor? Learn more: https://atlas.ripe.net/get-involved/become-an-anchor-host/ There are several organisations that want to host a RIPE Atlas Anchor but don’t have the necessary funding. Find out more about the RIPE NCC campaign to sponsor 15 RIPE Atlas Anchors https://labs.ripe.net/Members/alun_davies/campaign-to-sponsor-15-ripe-atlas… We would also like to remind you about our ongoing cooperation with APNIC, LACNIC, AFRINIC and ISOC: thanks to their help we are getting more geographical diversity to the measurement data. If your organisation is in their region contact us at <atlas(a)ripe.net> and we will get you in touch with them! And don’t forget to let us know by contacting us at <atlas(a)ripe.net> if you’re doing something interesting with RIPE Atlas data - we always want to hear about your use cases, research and experiences! Regards, Michela Galante RIPE NCC

1 0

Atlas anchor Error message in the Bootlog
by Stanish Stanishev 22 Feb '17

22 Feb '17

Hello, I've installed the software on our Atlas anchor, however I noticed the following error message in the Boot Log: Error adding default gateway 213.91.165.187 for eth0. (213.91.165.187 is the IP addr assigned as def GW, eth0 is connected to the router and it is Up) Has anyone faced this issue ? I've sent an email to atlas(a)ripe.net for troubleshooting assistance but nobody has replied so far. Thanks Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

Querying popular domains with RIPE Atlas
by Chris Amin 21 Feb '17

21 Feb '17

Dear colleagues, As you are probably aware, DNSMON* and RIPE Atlas built-in** measurements are often used when analysing outages and other issues with important DNS services, particularly the root zone servers. These measurements do not provide a direct indication of the impact on actual end-user experience because they involve directly querying authoritative name servers, thereby ignoring the effects of having multiple authoritative name servers as well as caching local recursive resolvers. To improve upon our DNS monitoring, we will initiate two built-in DNS measurements from all RIPE Atlas probes that use the probes' default resolvers instead of authoritative name servers. The first measurement will query for random top-level domains with the intention of avoiding caches and therefore hitting at least one root name server. The second measurement will query for popular domain names, with the intention of hitting caches where appropriate and getting an idea of the true impact on users. As a starting point for the second measurement, we will use a recent snapshot of the global top 50 visited sites according to the Alexa top sites list***, which combines unique visitors and individual page views in its calculations. Probes will cycle through these domains, querying for a different A record every 10 minutes. Since DNS queries containing these domains will be made from every connected RIPE Atlas probe, we would like to ask for feedback on whether querying the DNS for any of these domains could pose legal or political problems for probe hosts in certain parts of the world. I have also included the next 25 most popular domains below, which will be used to fill any gaps caused by removing items from the main list. Kind regards, Chris Amin RIPE NCC * https://atlas.ripe.net/dnsmon/ ** https://atlas.ripe.net/docs/built-in/ *** https://en.wikipedia.org/w/index.php?title=List_of_most_popular_websites&ol… Provisional 50 domains to query =============================== google.com. youtube.com. facebook.com. baidu.com. wikipedia.org. yahoo.com. google.co.in. amazon.com. qq.com. google.co.jp. live.com. taobao.com. vk.com. twitter.com. instagram.com. hao123.com. sohu.com. sina.com.cn. reddit.com. google.de. linkedin.com. tmall.com. yahoo.co.jp. weibo.com. google.fr. 360.cn. google.co.uk. google.ru. google.com.br. yandex.ru. ebay.com. bing.com. msn.com. google.it. soso.com. t.co. wordpress.com. google.es. microsoft.com. tumblr.com. aliexpress.com. blogspot.com. netflix.com. amazon.co.jp. ok.ru. google.com.hk. stackoverflow.com. google.ca. google.com.mx. imgur.com. Next 25 most popular domains, excluding pornography =================================================== apple.com. Naver.com. mail.ru. imdb.com. popads.net. onclickads.net. office.com. google.co.kr. github.com. pinterest.com. paypal.com. tianya.cn. google.com.tw. google.com.tr. google.com.au. diply.com. amazon.de. google.co.id. microsoftonline.com. onclckds.com. twitch.tv. adobe.com. amazon.co.uk. wikia.com. cnzz.com.

3 3

Reminder: Ten Days Left to Apply for "DNS Measurements Hackathon"
by Vesna Manojlovic 16 Feb '17

16 Feb '17

Dear colleagues, The fifth RIPE NCC hackathon will take place on Thursday and Friday, 20-21 April 2017, in Amsterdam. Apply online: https://atlas.ripe.net/hackathon/dns-measurements/#!application-form *The application deadline is 26 February 2017* Find out more in this RIPE Labs article: https://labs.ripe.net/Members/alun_davies/dns-measurements-hackathon-2017 Regards, Vesna Manojlovic RIPE NCC Community Builder

1 0