- ripe-atlas - mailman.ripe.net

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

Selecting only anchors for UDM
by Ondřej Caletka 12 Jun '14

12 Jun '14

Hello list, is there a way to run an UDM on Anchors only? I think it would be a good feature, especially for precise latency measurement. Cheers, Ondřej Caletka

10 18

Using RIPE Atlas to Debug Network Issues
by Vesna Manojlovic 12 Jun '14

12 Jun '14

Dear colleagues, Please find the use-case for RIPE Atlas in debugging network issues, in this RIPE Labs article written by Tim Kleefass from BelWü, who is hosting a RIPE Atlas anchor. (and who holds the record for the shortest time from purchasing the anchor to it going live!) https://labs.ripe.net/Members/tim_kleefass/how-fast-the-ripe-atlas-anchor-h… Regards, Vesna

1 0

Speed tests?
by Brian Rak 11 Jun '14

11 Jun '14

Are there any plans to allow testing download speed from the probes? I guess this could cause problems for people who have the probes on metered bandwidth plans.

12 12

Lemuria Communications (US) has joined RIPE Atlas anchors
by Michela Galante 10 Jun '14

10 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 us-dal-as7366 and it is hosted by Lemuria Communications in Dallas, United States. 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

Empty from feild
by john 06 Jun '14

06 Jun '14

Hello All, Quick question about the data format. What would cause a measurement to have an empty from field but contain data? An example would be probe_id 13663 from measurement 1672218[1]. A cursory glance seems to happens a lot more with V6 Thanks John [1]https://atlas.ripe.net/api/v1/measurement-latest/1672218/

3 4

NTT Communications (US, Seattle and Atlanta) have joined RIPE Atlas anchors
by Michela Galante 06 Jun '14

06 Jun '14

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by NTT Communications in United States, are: us-sea-as2914, in Seattle us-atl-as2914, in Atlanta Congratulations to NTT Communications for their third and forth anchor online! 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 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

A collection of tools in Perl
by Stephane Bortzmeyer 04 Jun '14

04 Jun '14

https://github.com/pierdom/atlas-toolbox

3 2

RIPN (RU) has joined RIPE Atlas anchors
by Michela Galante 03 Jun '14

03 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 ru-mow-as15835 and it is hosted by RIPN in Moscow, Russia. 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

Changes to the Distribution Model for RIPE Atlas Probes
by Vesna Manojlovic 03 Jun '14

03 Jun '14

Dear colleagues, we have made some adjustments in the distribution model of RIPE Atlas probes to ensure wider topological and geographical probe coverage. Please read more in this RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/changes-to-the-distribution-mode… Regards, Vesna

1 0

Probe not showing IPv6 ASN and subnet on map
by JC 02 Jun '14

02 Jun '14

Hi, We just setup our probe (id: 17328) and configured static IPv6 on it. Built-in measurements to IPv6 destinations seems to perform correctly from this probe. However, when we display detailed information about the probe on the coverage map https://atlas.ripe.net/results/maps/network-coverage/ we only see IPv4 information and no IPv6 subnet or ASN. Besides, searching for our IPv6 ASN (21538) in the filter field brings no results. Thanks for your help. Regards, JC

2 1

Where is "My probe" tab?
by Gilles Pion 28 May '14

28 May '14

Hello, Just received my probe today, Registered it, plugged it, all leds seem correct. I've followed the instruction on page https://atlas.ripe.net/get-involved/become-a-host/ where one can read: "Once we see that your probe is connected to the RIPE Atlas infrastructure, you'll be able to see it listed on the Public Probes page and, when you are logged in to the RIPE Atlas website, it will appear under the "My Probes" tab on that page. But, although logged on the web site I'm unable to find this "My Probes" tab on the "Public Probes" page Could someone help? -- Gilles

2 2

Bogal AB (SE) has joined RIPE Atlas anchors
by Michela Galante 28 May '14

28 May '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 se-got-as50168 and it is hosted by Bogal AB in Gothenburg, Sweden. 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

Measurement creation tools and library
by Matt Calder 28 May '14

28 May '14

Hi, I'm announcing a set of Python-based command-line tools/library for measurement creation available at https://github.com/USC-NSL/ripe-atlas. Since the focus is heavily on assisting measurement creation, I think that it should compliment Sagan nicely. It has been slowly under development for a while now but still has plenty of room to grow in supporting all of the options for different measurement types. Thanks, Matt

2 1

Feature you asked for: "latest results" API
by Vesna Manojlovic 27 May '14

27 May '14

Dear RIPE Atlas community, last week we enabled a new feature that quite a few people had an interest in: an API that lets you get up to 10 most recent results of any measurement: https://atlas.ripe.net/docs/measurement-latest-api/ We wrote an article with more details: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-resul… From the article: "This new feature could come in useful in a number of different situations, such as: - Creating a widget for a website that monitors a specific result in near real time, such as ping results from 100 probes around the world toward your own website - Monitoring your network by setting up an alert based on the average measurement result from the past hour - Staying aware of a major network event, such as an Internet outage in a certain region - DNS monitoring of your own domain, with configurable measurements using 10 RIPE Atlas anchors - Prototyping a script using RIPE Atlas data" Please let us know if you find other creative uses for this new API! If you develop custom code for configuring the results of this API, please share it at the GitHub RIPE Atlas Community repository: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib We would love to hear your success stories! Regards, Vesna

2 1

Unable to connect my probe
by Vincent Roussillat 27 May '14

27 May '14

Hello I've received my probe #16969 yesterday, registered it and tried to connect it behind my Orange Livebox here in France. It doesn't succeed to get connected and even doesn't get an IP from the DHCP server of my box (which delivers IP address to my other devices). I have tried this morning to connect it to another Internet access, at work and this failed too. Led #4 remains blinking. I can see in MyAtlas interface that the probe got connected just after the first boot, as I can see to request to DNS servers logged in the interface. May be, an upgrade began and got interrupted, leaving the probe in a strange state, I don't know... Anyway, what should I do now ? Request another probe ? Send this one back to the RIPE ? If so, where should I send it ? Regards.

2 1

Introducing: the new result parsing library (Sagan)
by dquinn 26 May '14

26 May '14

Hi everyone, in advance of the RIPE Meeting, I thought I'd let you all know about the new parsing library we've developed for use against measurement results. This was mentioned in a recent RIPE Labs article[1] but I thought it worth detailing here for those of you who aren't avid Labs followers. The idea is that you run every result you get through this handy Python library and out comes programmer-friendly Python objects. It supports the various changes in result format over time, and even does some of the heavy lifting for you like calculating ping median rtt, parsing the DNS abuf, or counting the traceroute hops. The project code is published on GitHub[2], and pull requests are welcome. Installation can be done via Pypi[3], and documentation is included in the module and available online[4] as well If you have any questions feel free to post to the list and one of us will see what we can do for you. [1] RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-resul… [2] Project: https://github.com/RIPE-NCC/ripe.atlas.sagan [3] Pypi: https://pypi.python.org/pypi/ripe.atlas.sagan/ [4] Documentation: https://atlas.ripe.net/docs/sagan/

3 3

RIPE Atlas use case on RIPE Labs: Evaluating new IXP peers
by Vesna Manojlovic 26 May '14

26 May '14

Dear colleagues, in this article Daniel Gomez explain how RIPE Atlas helped to evaluate new synaix's peering partners within an Internet Exchange Point and how this helped to improve customer services. Please find more details on RIPE Labs: https://labs.ripe.net/Members/daniel_gomez/basic-evaluation-of-new-ixp-peer… Kind regards, Vesna Manojlovic RIPE NCC

1 0

Atlas Latest
by john 23 May '14

23 May '14

Hi, I have been playing with the latest API over the past few days and it seems like there may be a cache in place. Is this the case? if so how long is it? Thanks John

2 2

Probe cannot connect from behind IDS/IPS with HTTPS inspection
by Ondřej Caletka 21 May '14

21 May '14

Hello list, I just observed strange behaviour of one Atlas probe. It was unable to connect to the control server from a corporate network. I suspect that some IDS/IPS appliance detects and drops probe attempt to use port 443 for non-TLS traffic*. I've tested it by trying to SSH to control server from within that network and it failed. However, normal SSH to port 22 works fine. It would be nice if the probe would be able to try more ways to reach the control server, eg. first attempt on port 443, second on port 22, third on some arbitrary high port number. I know that it would be better to put the probe in front of the firewall/IPS, but this is much more complicated in many corporate networks. *) At least it doesn't do MitM on HTTPs traffic. I've checked that too. Cheers, Ondřej Caletka

6 10

a thought about public probe page...
by Wilfried Woeber 21 May '14

21 May '14

I've got a small comments regarding the probes' overviw page at https://atlas.ripe.net/probes/ - for the country filter, top right, could the list of countries be sorted? Thanks, low prio :-) Wilfried.

1 0

Problems with DNS measurements and NSID
by Klaus Darilion 21 May '14

21 May '14

Hi! Whatever I try I fail to get the nameserver id. See measurement: https://atlas.ripe.net/api/v1/measurement/1666014/ But there is no NSID in the results: https://atlas.ripe.net/api/v1/measurement/1666014/result/ Am I doing something wrong, or is there a bug? Thanks Klaus

5 12

NTT Communications (US, Miami) has joined RIPE Atlas anchors
by Michela Galante 20 May '14

20 May '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 us-mia-as2914 and it is hosted by NTT Communications in Miami, United States. Congratulations to NTT Communications for their second anchor online! 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