- ripe-atlas - mailman.ripe.net

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

CEZNET, z.s.p.o has joined RIPE Atlas anchors
by Lia Hestina 12 Jul '14

12 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 cz-prg-as2852 and it is hosted by CEZNET, 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 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

2 1

Fwd: Deleting/editing a UDM: Not Owner
by Hendrik Visage 08 Jul '14

08 Jul '14

Good day, I'm trying to delete/stop/edit an UDM, but I get this error: Not Owner when I click on the settings tab. Screen grab: https://www.dropbox.com/s/p0u2oiboct3ut23/Screenshot%202014-07-03%2021.21.1… Any advice ideas how to do that? Thanks HEndrik

3 7

Fwd: monitoring RFC1918 IPs
by Hendrik Visage 07 Jul '14

07 Jul '14

Hi there, I'd like to monitor a couple of internal routes from one of my probes, but I get this error: Ping: Field 'target' : Measurement target "10.23.0.1" is invalid. Is that a limit somewhere? possible to relax that for probes owned/operated by me? Thanks HEndrik

4 4

How to find the correct ASN of a probe?
by Eravuchira, Steffie Jacob 07 Jul '14

07 Jul '14

Hello, The RIPE Atlas probe API [1] says that the probe with ID 14468 belongs to the ASN 6871. As per the RIPE stat API [2], the holder for ASN 6871 is PlusNet PLC,GB. I run a traceroute measurement from the same probe (Probe ID 14468) and the IP address of the second hop ICMP response is "86.4.10.1". But the RIPE stat API [2] shows that "86.4.10.1" belongs to the prefix announced by ASN 5089, NTL Virgin Media Limited,GB. Could someone tell me how I can find the correct AS which the probe belongs to? [1] https://atlas.ripe.net/api/v1/probe/?id=14468 [2] https://stat.ripe.net/ Kind Regards, Steffie

2 1

Probe connectivity status update interval
by Ondřej Caletka 04 Jul '14

04 Jul '14

Hello list, yesterday, we've deployed IPv6 in the network probe #16666 is located. The probe obtained its address via SLAAC and is world-pingable, however the Atlas system still haven't recognized the probe has IPv6 connectivity. When scheduling IPv6 UDMs for this probe, they are stuck in state "Scheduling" - see UDM #1694838 or #1694575. I guess that the system avoids scheduling IPv6 measurements to probes without IPv6 connectivity. How often is the connectivity status updated? Should we replug the probe to update its status? Cheers, Ondřej Caletka

1 0