- ripe-atlas - mailman.ripe.net

Re: [atlas] Paris-traceroute variations
by Radim Hrazdil 21 Apr '18

21 Apr '18

Hello all! I'm struggling to understand how is the number of paris variations reflected in the merasurement output. If I run paris-traceroute on my machine, the output of a single hop looks something like this: 6 P(16, 16) HOSTNAME (IP):0,1,2,3,4,9,10 4.534/6.072/15.130/2.957 ms HOSTNAME (IP):5,6,7,8 7.641/10.282/13.119/1.965 ms What I'm reffering to is this part: (IP):0,1,2,3,4,9,10, which says which probe packets 'visited' this particular router. I don't understand, how is this reflected in the measurement output. Moreover, I have never encountered situaton in which 'from' fields within one hop would differ. This would suggest that no load balancing has been encountered, but that seems unlikely to me. Thanks for any replies, Radim Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

No suitable probes error, and inconsistency between results and measurement status
by Vasileios Giotsas 20 Apr '18

20 Apr '18

Hi all, I have a number of traceroute measurements that end-up with status "No suitable probes". The documentation explains that this error is quite rare, the quote below is from https://atlas.ripe.net/docs/udm/ "No suitable probes: The measurement cannot currently be executed as defined due to a lack of available probes. This may be because you asked to use probes that don't exist (for example, probes in an AS in which there are no probes) or because all of the probes you requested were too busy to take on new jobs. This latter scenario is very rare however." In my case happens in all of my latest measurement request that ask for different probes. It also happens when I use the wizard in the web interface which selects the probes automatically. Even weirder, some of these measurements appear to have been completed when I check the API. For instance, measurement 12244352 has status 6 (No suitable probes), and the web interface doesn't show any results. But the API endpoint shows that it has been executed and returned results: https://atlas.ripe.net/api/v2/measurements/12244352/ I'd appreciate some pointers on how to resolve this issue. Thanks, Vasileios

1 0

how to mark probe as dormant
by Randy Bush 18 Apr '18

18 Apr '18

i have a probe, 2283, which has unplugged from its old home and is in suspended animation in a suitcase until it reaches its new home in a month or two. the location map will not let me pur it in the middle of the pacific. and i can not see how to mark it as dormant/down. clue bat please. randy

4 7

New on RIPE Labs: Creating One-off Measurements with Blaeu, by Stéphane Bortzmeyer
by Vesna Manojlovic 17 Apr '18

17 Apr '18

Dear colleagues, Yesterday we published an article by Stéphane Bortzmeyer, where he presents Blaeu, a set of tools to create one-off measurements, mostly to debug temporary issues. Please find more details on RIPE Labs: https://labs.ripe.net/Members/stephane_bortzmeyer/creating-ripe-atlas-one-o… Kind regards, Vesna Manojlovic RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurement Tagging
by Mirjam Kuehne 12 Apr '18

12 Apr '18

Dear colleagues, The new RIPE Atlas measurement tagging feature is now available. Please find more details in this new RIPE Labs article: https://labs.ripe.net/Members/chris_amin/ripe-atlas-measurement-tagging Kind regards, Mirjam Kühne RIPE NCC

1 0

Join Network Operators' Tools Hackathon 23-24. June 2018 in Dublin; organised by: iNOG & RIPE NCC
by Vesna Manojlovic 10 Apr '18

10 Apr '18

Dear colleagues, The seventh RIPE NCC hackathon will take place on Saturday and Sunday, 23-24 June 2018 in Dublin -- co-hosted by iNOG (Irish Network Operators Group), whose 16th edition is happening on Thursday, 21st June. The topic this time is: tools for network operators. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/becha/join-network-operators-tools-hackathon RIPE NCC hackathons are cooperative, and all source code developed during the event will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://www.ripe.net/participate/forms/apply/dublin-hackathon/ *The first application deadline is 1st May* We look forward to seeing you there! Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Result streaming lacking results
by Tim Wattenberg 14 Mar '18

14 Mar '18

Hi everyone, I'm working on a project where I create a measurement via API and immediately subscribe to the result stream as well as the metadata stream ( https://atlas.ripe.net/docs/api/v2/manual/measurements/result-streaming.html ). socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, sendBacklog: true}); socket.emit("atlas_subscribe", {stream_type: "metadata", msm: mid}); Now even with (and also without) the sendBacklog option enabled, I rarely get even close to receive all results (the measurement produces max. 10 in total, I received max. 4-5, often only one or even none). Same goes for metadata, where I sometimes get the action: creation event, but never a notification when the measurement is stopped. Another question in this context: When does a one-off measurement gets stopped? I also subscribed to (dis)connect, atlas_error and atlas_subscribed but they give no hint what could be going wrong. I also tried the replay feature, which did not work at all for me either: socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, startTime: <Time of creation>}); What am I doing wrong? Thanks, Tim Tim Wattenberg mail(a)timwattenberg.de +49 1578 8248731

2 1

API Keys problem?
by Daniel Ankers 09 Mar '18

09 Mar '18

Hi, Has there been a change in the way that API keys work for the measurement results API? I've got an API key which is granted permission to get results from a non-public measurement. When I do: curl -H "Authorization: Key $KEY" " https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start= 1520510400" (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get: {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}} This was previously working, but I'm not sure exactly when it stopped. I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned. Regards, Dan

4 5

New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives
by Mirjam Kuehne 02 Mar '18

02 Mar '18

Dear colleagues, In this article we present a new way to access the dataset on the RIPE Atlas platform. Instead of fetching individual results from measurements using the available APIs, you can now download files containing public measurements for a given day. Please find more details on RIPE Labs: https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data… Kind regards, Mirjam Kühne RIPE NCC

9 12

New on RIPE Labs: OpenIPmap - A Collaborative Approach to Mapping Internet Infrastructure
by Mirjam Kuehne 14 Feb '18

14 Feb '18

Dear colleagues, OpenIPmap, the RIPE NCC’s tool for geolocating core Internet infrastructure, has undergone a full architectural overhaul. With a new set of APIs and interfaces designed to cater to the needs of all users, the system integrates various methods for estimating the geographical locations of IXPs, core routers and other components of Internet infrastructure. In this, the first of two RIPE Labs articles on the topic, we look at the evolution of OpenIPmap from its inception to today: https://labs.ripe.net/Members/jasper_den_hertog/openipmap-a-collaborative-a… Kind regards, Mirjam Kühne RIPE NCC

1 0