- ripe-atlas - mailman.ripe.net

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