- ripe-atlas - mailman.ripe.net

1msec RTT to ipv6.google.com?
by Abreu, Alexandre, Vodafone Portugal 22 Jul '15

22 Jul '15

Hi all Anyone had any issues with wrong RTTs on IPv6 probes? I've setup a ping probe (ID#2143865) to ipv6.google.com and it's consistently giving 1msec RTT on the seismograph and the json file. It is physically impossible. This is the RTT I get on the CPE the probe is connected to: SEQ HOST SIZE TTL TIME STATUS 0 2a00:1450:4003:806::200e 56 59 12ms echo reply 1 2a00:1450:4003:806::200e 56 59 12ms echo reply 2 2a00:1450:4003:806::200e 56 59 12ms echo reply 3 2a00:1450:4003:806::200e 56 59 12ms echo reply 4 2a00:1450:4003:806::200e 56 59 12ms echo reply 5 2a00:1450:4003:806::200e 56 59 12ms echo reply Regards, Alexandre Abreu

5 7

Probe downtime alert for IPv6?
by Jeroen van der Ham 21 Jul '15

21 Jul '15

Hi, The portal offers a notification option for down time. I have a probe that is connected both over IPv4 and IPv6. The latter is through an IPv6 tunnel, which seems a bit flaky at times. I was hoping that the downtime notification would also hold for IPv6, but it turns out it doesn’t. Would it be possible that that be added? Thanks, Jeroen.

2 1

atlas.ripe.net site 302 redirect loop
by Yang Yu 20 Jul '15

20 Jul '15

I have been having this issue with every feature that requires logging in on https://atlas.ripe.net. For instance, when I try to create an API key, HTTP POST to /keys/create/ gets a 302 to https://atlas.ripe.net/login?next=/keys/create/, then the new GET results in another 302 to https://atlas.ripe.net/keys/create/ and back to https://atlas.ripe.net/login?next=/keys/create/ until the browser gives up on redirecting and throws an error. Tested on Chrome/Firefox with Ubuntu trusty and Windows 7. Tried on a different computer from a different continent, still the same issue.

3 2

BDIX (Bangladesh) has joined RIPE Atlas anchors
by Michela Galante 16 Jul '15

16 Jul '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called bd-dac-as24122 and it is hosted by BDIX in Dhaka, Bangladesh, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

1 0

Problem in stopping measuraments
by Elverton Fazzion 14 Jul '15

14 Jul '15

Hello, I've got a issue trying to stop a measurament. I used the RIPE normally last year and I started to use it again two weeks ago. I realized that one experiment was still running since last year and I tried to stop it by using the REST API as described in the documentation. Unfortunately, it did not work. Thus, I tried to stop in the web interface and it did not work either. I do not know how to proceed in order to stop it. The credits got negative even I denied this kind of situation in my profile. Anyone had the same problem? The measurament ID of my experiment is 1791052. Thank you, Elverton.

2 1

unable to delete measurements
by Александр 08 Jul '15

08 Jul '15

Hi devs! I just created a few measurements through web browser and now I can't stop them (red button). In the browser debug I see server response after i click on the button is 403 Forbidden. Measurement ids: 2072826 <https://atlas.ripe.net/measurements/2072826/>, 2072825 <https://atlas.ripe.net/measurements/2072825/>, 2072816 <https://atlas.ripe.net/measurements/2072816/>. -- Best regads, Alexander

2 2

Upcoming change to DNS IN/TXT query result
by Philip Homburg 07 Jul '15

07 Jul '15

Hi, This is to inform you about a change in a future release of the RIPE Atlas firmware that changes how 'IN TXT' records get decoded in DNS measurements. Currently, the JSON generated by the probe for TXT query looks like this: { "fw" : -1 , "time" : 1436282373 , "lts" : -1 , "name" : "stereo.hq.phicoh.net" , "dst_addr" : "130.37.15.35" , "af" : 4 , "src_addr" : "193.0.10.226" , "proto" : "UDP" ,"result" : { "rt" : 12.172,"size" : 219 , "ID" : 45298 , "ANCOUNT" : 1 , "QDCOUNT" : 1 , "NSCOUNT" : 2 , "ARCOUNT" : 2,"abuf" : "sPKEAAABAAEAAgACB2RyYWdvbnMEYWlveQJldQAAEAABB2RyYWdvbnMEYWlveQJldQAAEAABAAAOEABPJUhlcmUgYmUg/yBkcmFnb25zISBXaXRoIFwgYW5kICIgYW5kIH8IYXMgd2VsbC4fVGhyb3dpbmcgaW4ggCBmb3IgZ29vZCBtZWFzdXJlLsApAAIAAQAADhAABgNuczHAKcApAAIAAQAADhAABgNuczLAKcCXAAEAAQAADhAABIIlDyPAqQAcAAEAAA4QABAgAQRw0WoAEAKgyf/+nxep","answers" : [ {"TYPE" : "TXT" , "NAME" : "dragons.aioy.eu" , "RDATA" : "Here be \u00FF dragons! With \\ and \" and \u0008as well.\u001FThrowing in \u0080 for good measure."} ] } } Note that the '\u' escape sequence is used escape characters outside the safe ASCII range and that the code fails to support more than one string (the actual reply contains 3 strings). The '\u' notation seemed like a good idea at the time, but because it is valid JSON it is not always transparent and it triggered bugs in other software. The plan is to move to the following format: { "fw" : -1 , "time" : 1436282575 , "lts" : -1 , "name" : "stereo.hq.phicoh.net" , "dst_addr" : "130.37.15.35" , "af" : 4 , "src_addr" : "193.0.10.226" , "proto" : "UDP" ,"result" : { "rt" : 13.186,"size" : 219 , "ID" : 45298 , "ANCOUNT" : 1 , "QDCOUNT" : 1 , "NSCOUNT" : 2 , "ARCOUNT" : 2,"abuf" : "sPKEAAABAAEAAgACB2RyYWdvbnMEYWlveQJldQAAEAABB2RyYWdvbnMEYWlveQJldQAAEAABAAAOEABPJUhlcmUgYmUg/yBkcmFnb25zISBXaXRoIFwgYW5kICIgYW5kIH8IYXMgd2VsbC4fVGhyb3dpbmcgaW4ggCBmb3IgZ29vZCBtZWFzdXJlLsApAAIAAQAADhAABgNuczHAKcApAAIAAQAADhAABgNuczLAKcCXAAEAAQAADhAABIIlDyPAqQAcAAEAAA4QABAgAQRw0WoAEAKgyf/+nxep","answers" : [ {"TYPE" : "TXT" , "NAME" : "dragons.aioy.eu" , "RDATA" : [ "Here be \\255 dragons! With \\092 and \\034 and \\127", "as well.", "Throwing in \\128 for good measure." ] } ] } } Here the escape sequence is similar to the one in DNS zone files. Except that the backslash has to be doubled in JSON. Furthermore, after RDATA comes a list of strings instead of a single string directly. For anyone who parses the JSON output directly, the change from a single string to a list of strings is probably the biggest change. Similar changes will be made in the Sagan package. There, python tricks may hide the list if the result is used in a string context. Philip

1 0

Get the list of all probes?
by Stephane Bortzmeyer 07 Jul '15

07 Jul '15

For a project (testing the randomness of probe selection), I need a list of all probes. The only solution I find is a loop over <https://atlas.ripe.net/api/v1/probe/?limit=100&offset=N> Is there a simpler way? <https://atlas.ripe.net/docs/api/#public-probes-list> seems to say there is a JSON file with all probes but it yields a 404 (reported to the RIPE-NCC, ticket [ripe.net #1179513])

2 3

LLDP / LLDP-MED support?
by Pekka Järvinen 07 Jul '15

07 Jul '15

Hi, Would there be any idea to add LLDP support to probes? -- Pekka Järvinen

3 2

Fwd: Your RIPE Atlas Probe (ID: 22769) is not connected to our network
by Jonathan Brewer 07 Jul '15

07 Jul '15

Hi There, My probe 22769 appears to be malfunctioning, and I'm not sure what to do in terms of diagnostics. >From the router nearest it on the network: https://www.dropbox.com/s/ghe4e3tz69u1kvc/Screenshot%202015-07-07%2011.30.1… Looks to me as if it's rebooting frequently, but I have no way to check without an in-person visit. Do you have any suggestions as to how to troubleshoot? I have access to the network it's on. Thanks, Jon ---------- Forwarded message ---------- From: RIPE Atlas <no-reply(a)ripe.net> Date: 6 July 2015 at 07:40 Subject: Your RIPE Atlas Probe (ID: 22769) is not connected to our network To: jon.brewer(a)gmail.com Dear RIPE Atlas probe host, Thank you for participating in RIPE Atlas! We have noticed that your probe (#22769 with description MDC) is not connected to our infrastructure and has been disconnected since 2015-06-28 22:42 UTC. Could you please check whether everything is set up correctly on your side? If it is, and your probe is still reported as disconnected when you log in at https://atlas.ripe.net, please reply to this email so that we can follow up. You can review the instructions for setting up your probe at https://atlas.ripe.net/getting-started If you have any questions, please contact us at atlas(a)ripe.net Best regards, RIPE Atlas Team ********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.

1 0