- ripe-atlas - mailman.ripe.net

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

tracing from anchor nodes
by Klaus Darilion 02 Jul '14

02 Jul '14

Hi! According to DNSMON [1] r.ns.at IPv4 is not reachable from us-bos-as11488. Are there any tools available to analyse the problem from the anchor? E.g. performing a traceroute from the respective anchor node? Thanks Klaus [1] https://atlas.ripe.net/dnsmon/group/at.?dnsmon.session.color_range_pls=0-66…

3 3

Paris-traceroute variations
by Juan Antonio Cordero Fuertes 30 Jun '14

30 Jun '14

Not sure this is the right place to ask this... sorry if it is not. I'm trying to configure Paris-traceroute measurements, and it is not clear for me what is the meaning of the *paris* parameter. In https://atlas.ripe.net/docs/udm/ it is said that it corresponds, for values from 1 to 16, to "the number of variations to be used for a Paris traceroute <http://www.paris-traceroute.net/>". What is this? Does it correspond to the number of initial probes to be used by paris-traceroute? I am unable to figure it out from the RIPE Atlas docs... any indication would be appreciated. Thanks, Juan Antonio Cordero

5 8

IPv6 ICMP - denied packets
by Joachim Tingvold 24 Jun '14

24 Jun '14

Hi, I recently installed a probe at home, and now my router spits out loads of 'denied icmpv6'-messages. After going through the logs for the last two days, I have ~1900 entries of denies towards the probe -- all of them more or less like this (with different source); ### Jun 22 2014 22:30:22.863 CEST: %IPV6_ACL-6-ACCESSLOGDP: list ipv6-inbound/2100 denied icmpv6 2A01:4F8:130:24A4::13:76 (Po1.102) -> {PROBE-IPV6-ADDRESS} (1/4), 8 packets ### I've got an ACL applied ingress on the link to my ISP, and the relevant part is shown below; ### ipv6 access-list ipv6-inbound sequence 2000 permit icmp any any echo-reply sequence 2005 permit icmp any any echo-request sequence 2010 permit icmp any any packet-too-big sequence 2015 permit icmp any any time-exceeded sequence 2020 permit icmp any any destination-unreachable sequence 2025 permit icmp any any parameter-problem sequence 2100 deny icmp any any log-input ### This ACL conforms to RFC4890[1] (except the Mobile IPv6 part). Of the 1900 entries, all of them are ICMPv6 type 1. ~300 of them have the code bit[2] set to 1, and ~1600 of them are set to 4. These are the top sources; ### 367 2001:500:2::C 313 2001:500:2D::D 289 2A01:4F8:130:24A4::13:76 289 2001:500:3::42 196 2A01:4F8:121:30A4::78:15 161 2001:DC3::35 100 2001:7FE::53 67 2001:7FD::1 60 2001:500:2F::F ### All of these are DNS root servers (except those starting with 2A01:4F8, which are some Atlas-thingies). It seems to me that the Atlas-probe sends quite some amount of ICMPv6-packets to the root DNS-servers (and even Atlas' own boxes), that are being returned with errors. Why does the probe do this, and does it actually rely on these replies? [1] <http://www.ietf.org/rfc/rfc4890.txt> [2] <http://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xml#icm…> -- Joachim

3 3

AFRINIC (MU) has joined RIPE Atlas anchors
by Michela Galante 18 Jun '14

18 Jun '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 mu-plu-as327681 and it is hosted by AFRINIC in Port Louis, Mauritius. This is the third anchor hosted by an RIR on behalf of the RIPE NCC. 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

1 0