- ripe-atlas - mailman.ripe.net

New on RIPE Labs: Midsummer Update for RIPE Atlas
by Vesna Manojlovic 24 Jul '14

24 Jul '14

Dear colleagues, in these hot and slow summer days, we give you an overview of the current status of RIPE Atlas, new features since the last update during RIPE68, and an insight into past and future community activities: https://labs.ripe.net/Members/fatemah_mafi/ripe-atlas-midsummer-update-2014 Regards, Vesna -- Measurements Community Building team <MCB(a)ripe.net>

2 1

some thoughts and question regrding probe "stability"
by Wilfried Woeber 22 Jul '14

22 Jul '14

Hi Folks, triggered by the discussion related to DNSMON, and an issue (power, resolved) with one of my V1 probes, I'd like to get some input or start a disussion or an investigation. To start with, I am not very clear what the term "stability" w/should mean in this context, as the probes are supposed to buffer measurment data locally, at least for a while (true?). So, here goes... Obviously, looking at some Atlas Stat pages, there are probes with a 100% uptime. Now, looking a the 3 under my supervision (2x V1, 1 Anchor), ref "Connected" and "Disconnected", there's no chance to get near that value, as all of them tend to topple over on a regular basis, mostly for a *short* period of time in the range of 0m(!) to some 30+m. With respct to the bahaviour of the Anchor, which is mounted in the same rack as the backbone router it connects to, in a Data Center, we tried to correlate the (reported) disconnection events with the router and interface logs for the probe. No luck there, also, no maint works or the like, so I presume the Anchor didn't reboot or that there were "real" network problems. Let's compare the most recent dis/connection logs for my 3 pets: ID 6009 2014-07-14 03:58:03 3d 8h 16m Still Connected 2014-05-27 03:03:54 48d 0h 46m 2014-07-14 03:50:47 0h 7m 2014-05-20 15:19:02 6d 11h 37m 2014-05-27 02:57:00 0h 6m 2014-05-14 21:16:56 5d 17h 59m 2014-05-20 15:16:22 0h 2m 2014-04-08 16:03:21 36d 5h 1m 2014-05-14 21:05:17 0h 11m ID 0466 2014-07-13 23:31:05 3d 12h 45m Still Connected 2014-07-09 23:05:40 3d 23h 54m 2014-07-13 22:59:49 0h 31m 2014-06-16 10:53:21 23d 11h 55m 2014-07-09 22:49:04 0h 16m 2014-05-25 09:03:06 22d 1h 38m 2014-06-16 10:42:00 0h 11m 2014-05-24 20:34:50 11h 54m 2014-05-25 08:29:12 0h 33m ID 0414 2014-07-07 23:41:23 9d 12h 35m Still Connected 2014-07-02 03:58:45 5d 19h 31m 2014-07-07 23:29:54 0h 11m 2014-06-13 09:37:50 18d 18h 7m 2014-07-02 03:45:08 0h 13m 2014-06-08 13:22:14 4d 20h 7m 2014-06-13 09:29:38 0h 8m 2014-05-21 08:29:23 18d 4h 45m 2014-06-08 13:15:11 0h 7m Again, I fail to see some obvious correlation, what am I missing? Does anyone else see a similar pattern? How to start debugging, if there's anythig that needs debugging? Thanks for your ideas and help! Wilfried

9 13

Actual public measurements
by Brian Rak 22 Jul '14

22 Jul '14

Is there any way to link someone to a public measurement, without requiring that they go and sign up for a RIPE account? It's an annoying extra step when I'm just trying to show someone the results of a measurement. I'm aware I could grab that raw data via the API, but then I'd have to re-implement the UI... which I don't have time for.

3 2

Questions about paris traceroute
by Thomas Holterbach 18 Jul '14

18 Jul '14

Hi all, I would like to start some Paris-traceroute measurements from RIPE Atlas probes, with a specific frequency and a control over the paris id. In particular, I am wondering if it is possible to start a traceroute measurement with all the 16 paris id at the same time. Because so far, I only find out how to start periodically a traceroute with a different paris id. I am also a little bit confused about the interval between two measurements. In the doc, it is written that the default value (900s) is the minimum, but when I create a UDM, the minimum interval seems to be 60s. I also tried 10 secondes with Restful API and the measurement started, but the real interval seems to be far upper than 10s. Can you give me more informations about this interval ? Thank you for your help, Thomas.

5 6

adding probes to UDM
by Jared Mauch 17 Jul '14

17 Jul '14

I have a few ongoing UDMs and there’s a few things that have occurred over the duration: 1) I requested 5 probes and only 3 were available (at the time). Is there a way to request the system consider more? 2) I requested 5 probes and 5 were available, but some have fallen out (and are now crossed out). I want to request 1 or 2 more to get back to the 5 threshold so I feel I have more accurate data. Are either of these possible, or do I need to stop these and create a new UDM with a larger number of probes to keep a more stable population over time? (They have been running for ~2 months so far). - jared

2 1

Three new Anchors have joined the RIPE Atlas network
by Lia Hestina 15 Jul '14

15 Jul '14

Dear RIPE Atlas users, We proudly announce three new RIPE Atlas anchors have joined the network and are now available as target for probe hosts conducting their own user-defined measurements. The new anchors are called: be-anr-as2611 is hosted by MOSAIC - University of Antwerp - iMinds uk-lon-as60157 is hosted by Antheus Telecom LTD us-wct-as7922 is hosted by Comcast Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Credit Usage math
by Jared Mauch 15 Jul '14

15 Jul '14

I am in the lucky position of earning more credits than I currently care to spend so have engaged in a bit of a 'share the wealth' campaign. (Yes, you can ask me for credits, but I am hoping something can be done to improve this as well, read on). I just sent 1 million credits to someone and now my credit "burn" rate is calculated as a large negative number. (I recently sent someone else 10x that and it caused odd math as well). It seems a few things happen: 1) E-Mail alerts go out based on credit consumption (including transfers) in past N hours. 2) Credit "earn rate" calculation includes transfers vs UDM samples. Currently I have income of almost 1M/day but shows -4k/hour due to UDM + transfer. This means when I sent 10m credits to someone, the system thought I was using 10m credits/day and emailed me a few times because it thought I would run out of credits when my UDMs gave me a few more weeks of time with my balance. I also have a large number of "small" UDMs which post quite often, so have 397 pages of the recent credit history. Are there plans to improve this display? - Jared

2 1

Local resolver for one off DNS measurement
by Rob Turner 15 Jul '14

15 Jul '14

Hi is it possible to perform a one off DNS A record test that uses each probes local resolver? I think this would be handy to test DNS propagation. Rob.

2 1

Solido Networks ApS has joined RIPE Atlas anchors
by Lia Hestina 14 Jul '14

14 Jul '14

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 dk-blp-as59469 and it is hosted by Solido Networks ApS in Ballerup, Denmark. Our congratulations to Solido Networks ApS! This is the first anchor in Denmark. In our announcement about last week's new anchor, there was a typo in the company name and we would like to apologise for this. The anchor, cz-prg-as2852, is hosted by CESNET, z. s. p. o. in Prague, Czech Republic. 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: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Atlas nagios tools
by john 12 Jul '14

12 Jul '14

Hello all, i would like to introduce a tool[1] i have been developing on and off for a bit of time. its uses the atlas latest call[2] and sagan[3] to preform nagios checks based on measurement results. it supports checking a wide range of ssl, dns and http parameters which i have tried to document on github[1]. it also supports checking ping however i think it is better to use the atlas status checks[4][5] for this. The git hub repo contains some sample nagios configs which can be seen in action at https://icinga.johnbond.org/ (ripeatlas/ripeatlas). at $dayjob we dont use nagios/icinga so this is not well tested and one should expect some bugs. if you dare inspect the source you can definitely expect spelling mistakes and hacks. Thanks to Iñigo Ortiz de Urbina and Wolfgang Nagele for patches. Also thanks to Daniel Quinn and Philip Homburg for working with me integrating some changes to sagan. feedback, criticism and patches most welcome John *as http is a restricted measurement this has received little testing [1]https://github.com/b4ldr/atlas [2]https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-res… [3]https://github.com/RIPE-NCC/ripe.atlas.sagan [4]https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atla… [5]https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob…

1 0