- ripe-atlas - mailman.ripe.net

New on RIPE Labs: TraceMON - Network Debugging Made Easy
by Mirjam Kuehne 11 Apr '17

11 Apr '17

Dear colleagues, TraceMON is a client-side tool for visualising network topology generated by traceroutes reaching one or more targets in a network. It provides a one-click access to a set of information useful during day to day operations. Please find more details on RIPE Labs: https://labs.ripe.net/Members/massimo_candela/tracemon-traceroute-visualisa… Kind regards, Mirjam Kuhne RIPE NCC

3 3

Problems trying to add a probe to a measurement
by Colin Strutt 07 Apr '17

07 Apr '17

I'm trying to add a probe, by probe number, to an existing, running measurement, using curl, following the example and description on page 84 of the "RIPE Atlas API v2 manual". However, I'm getting an error message that does not clearly point me to the problem, and thus allow me to correct my error. Here's what I'm entering (with the <.> as placeholders, explained below) curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST -d '{"probes":[{"action":"add","requested":1,"type":"probes","value":"<p>"}]}' https://atlas.ripe.net/api/v2/measurements/<m>/participation-requests/?key=< a> where: <p> is the number of the probe I'm trying to add, and I can access it at https://atlas.ripe.net/probes/<p> <m> is the measurement to which I'm trying to add it - it's a running measurement, and I can access it at https://atlas.ripe.net/measurements/<m> <a> is the API key, which is enabled and has "Update an existing measurement" granted The error I get back is: {"error":{"status":400,"code":104,"detail":"JSON parse error - No JSON object could be decoded","title":"Bad Request"}} In case it's relevant, I'm running curl 7.53.1 on Windows 10. Thanks in advance for any suggestions. colin

2 2

ipad air
by mostafa 23 Mar '17

23 Mar '17

Sent from my iPad

1 0

New on RIPE Labs: Update on First Five Sponsored RIPE Atlas Anchors
by Alun Davies 23 Mar '17

23 Mar '17

Hello all, We just released a RIPE Labs article giving an update on the RIPE NCC’s campaign to sponsor fifteen RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-… <https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-…> Best regards, Alun Davies RIPE NCC

1 0

Measuring SCTP and DCCP compatibility
by Felix Konstantin Maurer 22 Mar '17

22 Mar '17

Hi, I'm interested in measuring the support of new transport protocols in consumer routers. As IPv6 does not need rely on NAT anymore, most routers probably only have a firewall for IPv6 traffic. I assume that these firewalls drop traffic they do not understand, but I'm curious to see if it is actually true, or whether we have the possibility to use new transport protocols now. As far as I can see, there are only a limited number of possible measurements possible with Atlas probes. Do you think they could be extended to be more flexible and for example allow measurements using SCTP? Regards Felix

1 0

Cannot understand the daily limit
by Stephane Bortzmeyer 22 Mar '17

22 Mar '17

RIPE Atlas just denied me a measurement: "{"error":{"status":400,"code":104,"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000 credits. Please stop some of your currently running measurements and try again.","title":""}}" I have one permanent measurement, which takes, according to <https://atlas.ripe.net/user/credits/>, 3400 credits/hour (81600/day). Otherwise, I ran only one-off measurements, most taking < 1000 credits. How could I hit a limit of ONE MILLION per day?

3 7

Starting again a stopped custom measurement
by Sylvain Pascou 22 Mar '17

22 Mar '17

Hello, This might seem like a silly question but I've found no way, whether through the Web UI or the POST API, to start a measurement that I have previously accidentally stopped. Is this a problem or simply a not-implemented feature? Sylvain Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 2

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