- ripe-atlas - mailman.ripe.net

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 06 Jul '15

06 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

API to get information about a probe?
by Stephane Bortzmeyer 06 Jul '15

06 Jul '15

I cannot find an API to retrieve information about a probe. I would like to get the information I can see on, for instance, <https://atlas.ripe.net/probes/10644/> but from a REST + JSON API. Does it exist? Do you think it would be a nice addition? (My current use case is that I find some probes failing to ping a target and I would like to quickly check if they share something, such as ASn or some tags.)

2 3

Wrong IP prefix values accepted?
by Stephane Bortzmeyer 05 Jul '15

05 Jul '15

It seems there is no protection against wrong prefixes? See measurement #1897909, which started with JSON: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of jihadmin.com from prefix foobar', 'af': 4, 'query_argument': 'jihadmin.com', 'query_type': 'A', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 3, 'type': 'prefix', 'value': 'foobar'}]}

2 5

Fwd: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear all, The following article might be of interest to you. Regards, Robert -------- Forwarded Message -------- Subject: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing? Date: Thu, 02 Jul 2015 12:18:55 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see what eyeball networks are missing out on RIPE Atlas probes: https://labs.ripe.net/Members/emileaben/improving-ripe-atlas-coverage-what-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Probe and measurement archives vs. the APIs
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear All, We've observed recently that some users are using scripts to "crawl" through all the metadata provided by the probe and measurement APIs. This means that some people out there download basically the entire probe and/or measurement meta data set the system provides. As you can imagine, this is highly inefficient and keeps our servers busy. We believe that there could be better solutions. We have been providing the downloadable archive for probe metadata for some time now, and recently we've added the measurement metadata too. You can now reach these at http://ftp.ripe.net/ripe/atlas/ This way one can even get complete sets of metadata as far back as January 2015 for measurement specifications and March 2014 for probe data. Given the existence of these archives, we will apply a sane limit on how much metadata can be reached via the APIs. In practice this means that the API will not allow fetching results beyond, say, 10.000 (i.e. 500 pages of 20) entries. This is after the application of filters, so for example with no filters at all you could still access metadata of the 10k newest measurements, while if you filter for DNS measurements only, you could get the 10k newest of those, and so on. We believe this keeps the metadata API useful for the majority of the users, while the existence of the archive serves the remaining cases. Our plan is to make this change around the end of July. Regards, Robert Kisteleki

1 0

RIPE Atlas traceroute visualisation - use cases
by Massimo Candela 01 Jul '15

01 Jul '15

Hello, We are creating a tool to visualise traceroute results coming from the RIPE Atlas measurement network. The tool will of course be available to everyone. To help make this tool as useful as possible, I’m gathering use cases of day-to-day operations and research activities that use traceroute measurements. I hope you can spend a few minutes to answer this email and tell me how you use traceroute measurements or what you would like to have in such a tool. For each use case you have in mind, please describe it briefly. Keep in mind our system can collect measurements from multiple sources to a single target repeatedly (e.g. every 60 seconds). Don’t focus only on traceroute data, but also on correlations among traceroutes and BGP, RTT, geolocations, DNS, and registry information (feel free to expand the list to other datasets). Thanks for your time. Your help is invaluable. Ciao, Massimo RIPE NCC

2 1

DHIRAAGU (Maldives) has joined RIPE Atlas anchors
by Michela Galante 30 Jun '15

30 Jun '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 mv-mle-as7642 and it is hosted by DHIRAAGU in Male, Maldives, 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

Re: [atlas] vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

low vm disk use is priority low vm memory is priority colin Sent from my iPhone > On 30 Jun 2015, at 11:15, RIPE Atlas <atlas(a)ripe.net> wrote: > >> On 2015-06-22 15:03, Colin Johnston wrote: >> any news on vm image for ripe atlas probe ? >> would be great to use as could monitor vm farms much better ? >> >> Colin. > > Dear all, > > We understand that some people asked for this feature. At the moment we're > evaluating it, and plan to come back to the community with a plan of action > before the end of August. It's possible that we'll post a couple of > clarification questions in the meantime. > > Regards, > Robert

1 0

vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

any news on vm image for ripe atlas probe ? would be great to use as could monitor vm farms much better ? Colin.

5 4

Active probes
by Ben O'Hara 25 Jun '15

25 Jun '15

Hi, We currently pull https://atlas.ripe.net/contrib/active_probes.json as part of some analysis of atlas data, this seems to have gone missing since yesterday and now returns a 404. Is this known? Should it work? Will it come back? Cheers Ben BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo]<http://www.bomboratech.com.au/> www.bomboratech.com.au<http://www.bomboratech.com.au/> Follow us on Twitter<https://twitter.com/BomboraTech> The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

2 2

Probe update
by Laurent Dumont 23 Jun '15

23 Jun '15

Hi gents, Small update on the probe status. I've tried a 2A usb power adapter and no dice. The Power and WPS led come on and a ethernet link seems to be active between the probe and the switch. Unfortunately, there is no DHCP discover or any kind of network activity from the probe. Anything else I can try to troubleshoot this? Is there a LED guide somewhere? -- Laurent Dumont coldnorthadmin.com

2 1

Probe question - Issue
by Laurent Dumont 23 Jun '15

23 Jun '15

Hi gents, After some delay, I'm trying to setup the probe I received. Unfortunately, it seems that something is not quite working. Once it's plugged in and powered, there is no activity. There is no DHCP request for the probe so I can't see anything on the network side. Could something be wrong with the usb key? Is there a way I could reflash the usb key with the OS files? Thanks Laurent Dumont -- Laurent Dumont coldnorthadmin.com

3 4

Netzwerge Hamburg eK, Hamburg, Germany has joined RIPE Atlas anchors
by Eamonn Lane 23 Jun '15

23 Jun '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 de-ham-as201709 and is hosted by Netzwerge Hamburg eK, Hamburg, Germany. 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 RIPE NCC atlas(a)ripe.net

1 0

FHE3 Gmbh, Frankfurt Am Main, Germany has joined RIPE Atlas anchors
by Eamonn Lane 23 Jun '15

23 Jun '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 de-fra-as49024 and is hosted by FHE3 Gmbh, Frankfurt Am Main, Germany. 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 RIPE NCC atlas(a)ripe.net

1 0

Enabling Data Compression in RIPE Atlas
by Vesna Manojlovic 19 Jun '15

19 Jun '15

Dear colleagues, We’d like to enable gzip compression on all of RIPE Atlas' measurement API calls — but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements — including the small number of measurements not marked as “public”. We believe the drawbacks are negligible, but we’re looking for community support. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/daniel_quinn_39/enabling-data-compression-in-… Regards, Vesna Manojlovic

1 0

atlas anchor DANE records
by Bjørn Mork 17 Jun '15

17 Jun '15

Hello, I just noticed "We also generate a DANE record for each anchor" in the docs and became instantly curious. There aren't that many DANE records out there in the wild :) The records seem to be pointing to a self signed certificate (as documented), but with 'usage' = 1 instead of 3 as expected. At least the two records I looked at had this - I assume they are all created the same way. Is this intentional? It makes 'normal' verification fail: bjorn@canardo:~$ tlsa --debug --verify nl-ams-as3333.anchors.atlas.ripe.net Received the following record for name _443._tcp.nl-ams-as3333.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 88422d55424ca8f6f74e165016851cb195fc0919f82f8762574a4d71868964e9 This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 193.0.19.107 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net Got the following IP: 2001:67c:2e8:11::c100:136b FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net bjorn@canardo:~$ tlsa --debug --verify se-sto-as8674.anchors.atlas.ripe.net Received the following record for name _443._tcp.se-sto-as8674.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 2d92e341d2181011c520ad92229155e1350fc4f7b9e628198be1f9589ec7a53f This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 185.42.136.158 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net Got the following IP: 2a01:3f0:0:60::5 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net What is the intended use of these records? And why doesn't https://atlas.ripe.net/ have a DANE record as well? :) Bjørn

1 0

HTTP Measurements with RIPE Atlas
by Vesna Manojlovic 17 Jun '15

17 Jun '15

Dear colleagues, After a discussion with the community about HTTP measurements, RIPE NCC will start implementing this as a publicly available measurement type. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas Kind regards, Vesna Manojlovic RIPE NCC

3 2

Atlas Anchors and LogJam
by Ben O'Hara 15 Jun '15

15 Jun '15

Hi, We host an Atlas Anchor, but our network monitoring still shows it being vulnerable to Logjam. Can you please let us know when this will be upgraded to fix the vulnerability? Cheers BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo]<http://www.bomboratech.com.au/> www.bomboratech.com.au<http://www.bomboratech.com.au/> Follow us on Twitter<https://twitter.com/BomboraTech> The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

2 1