- ripe-atlas - mailman.ripe.net

New on RIPE Labs: Amsterdam Power Outage as Seen by RIPE Atlas
by Vesna Manojlovic 31 Mar '15

31 Mar '15

Dear colleagues, As you might have heard, there was a power outage last week Friday in the north of The Netherlands, a country with a very high density of RIPE Atlas probes. This density provides us with some interesting data and visualisation. You can find more details on RIPE Labs: https://labs.ripe.net/Members/andreas_strikos/amsterdam-power-outage-as-see… Kind regards, Vesna

2 1

probes on VMs
by Klaus Darilion 30 Mar '15

30 Mar '15

Hi! I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud. For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources. Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes. regards Klaus

4 4

NAT conntrack invalid ICMP(v4) type 11 code 0 packets dropped by edge router
by Gary Gapinski 30 Mar '15

30 Mar '15

2 1

Create new measurement from old measurment
by Klaus Darilion 30 Mar '15

30 Mar '15

Hi! Is there a simple way in the webinterface to start a new measurement identical to an old one? (just duplicate them with new start-stop settings, in my case I want to duplicate one-off measurements) Thanks Klaus

2 2

Short and immediate report from the RIPE Atlas hackathon
by Vesna Manojlovic 30 Mar '15

30 Mar '15

We had the first RIPE Atlas hackathon! Three days of intensive coding, cooperating, learning, connecting and having fun (& surviving massive power outage on Friday in Amsterdam) - - and the results have bee impressive! Ten final projects have been presented, and four have been chosen as worthy of the awards: 1. Disco: Combining the visalization of disconnection-events with localized Twitter feed & live weather data 2. Spatial Bucketing of RIPE Atlas Probes on Map Projections (aka Picketty — making the global probe selection more equal) 3. Traceroute stability check & BGP+traceroute (two projects sharing the 3rd place) We had 24 participants & 1 no-show, 6 jury members and 11 support staff (coincidentally: 42!) On behalf of the community, we are grateful to Comcast for sponsoring prizes and travel expenses, hackerspace Technologia Incognita for the inspiring location on Friday, and to RIPE NCC for the office facilities during the weekend, staff support, food & drinks & amazing data & tools & platform of RIPE Atlas. On behalf of the organizers (RIPE NCC & Comcast), we are grateful to everyone who took part & contributed, as well as to their family & employers, who let them get away for the weekend of combined work&fun. Longer and more detailed report will follow, once we all get some sleep & collect our notes from tweets, IRC, mailing list & pieces of papers. Cheers, Vesna

2 1

What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
by Philip Homburg 27 Mar '15

27 Mar '15

Dear community members, The RIPE Atlas team has a question what to do with probes that have only a Unique Local IPv6 Unicast Address (ULA) [RFC4193] as their IPv6 address. The question is whether to treat those probes as IPv6 capable or not. It is known that about 10% of the RIPE Atlas probes that have IPv6 addresses do not actually have IPv6 connectivity. This was documented by Stéphane Bortzmeyer in his RIPE Labs article "How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)?" (https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-bel…) As a way of dealing with this problem, the RIPE Atlas system now tags probes that have broken IPv6. Any probe that has an IPv6 address (other than link local) but cannot reach the global internet is tagged as "IPv6 Doesn't Work" (see https://atlas.ripe.net/docs/probe-tags/) At the moment, around 2800 probes are connected and have an IPv6 address. Of those probes, around 350 (12.5%) are tagged that IPv6 doesn't work. Of those 350 probes, 114 have the surprising condition that the connect system call fails immediately with the error 'Network is unreachable.' Those 114 probes have two things in common, they have only a ULA address and the do not have a default route. It is the lack of default route that causes the connect system call to fail immediately. This feature (ULA and no default route) is specified in RFC-7084 (IPv6 CE Router Requirements) requirement ULA-5 ("An IPv6 CE router MUST NOT advertise itself as a default router with a Router Lifetime greater than zero whenever all of its configured and delegated prefixes are ULA prefixes.") The surprising thing is that for some probes this condition persists for many months. For the Atlas project, the question is how we should treat these probes. Currently they are regarded as having broken IPv6 connectivity. However, an alternative is to consider those probes as having no IPv6 at all. Broader questions are: are CPEs doing the right thing here. Should a CPE announce a ULA on the local LAN even if there hasn't been any IPv6 internet connectivity for a very long time? It is already complex enough for normal users to understand that there is always a link local IPv6 address even if there is no IPv6 connectivity. Now we have to add ULA to that group as well. So the question to the community, should RIPE Atlas treat ULAs in the same way as RFC-1918, addresses that should be ignored unless a valid global address can be found elsewhere. Or should we keep the current approach where ULAs are treated just like other global IPv6 addresses and consider the probe host's network setup to be broken? Philip

15 31

Paris-traceroute flow identifier
by Ibrahim Coskun 26 Mar '15

26 Mar '15

Hello, This is Ibrahim Ethem Coskun from University of Nevada, Reno. I'm currently working on an Internet Measurement project with Professor Mehmet Hadi Gunes. We are modifying paris-traceroute's source code and set the flow identifier of each packet (both sending and returning packets) to a constant value for every traces. So that, we want a trace to follow the same path whenever we traceroute the same target. However, I get the below warning messages from each probe : paris-traceroute -T 500 -i -l -M 5 -p icmp -r 44000 -a hopbyhop -n " + target_ip [WARN](TracertImpl.cc, 335)ICMP reserved words 0 0 0 0 0 [WARN](TracertImpl.cc, 330)Bad return flow id 0xd24e from 4.69.152.80 So, what does this warning mean, I checked the source code but couldn't find and information regarding this issue, I also email paris-traceroute team, but no responses. I googled my question and found a similar question emailed to to you ( https://www.ripe.net/ripe/mail/archives/ripe-atlas/2012-July/000534.html) I would be very pleased if you can answer my question. Thank you;

2 1

FranceIX ( Paris, France) has joined RIPE Atlas Anchors
by Alastair Strachan 26 Mar '15

26 Mar '15

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 fr-par-as57734 and it is hosted by FranceIX in Paris, France. 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

CarrierColo / IPB GmbH in (Berlin, Germany) has joined RIPE Atlas Anchors
by Alastair Strachan 25 Mar '15

25 Mar '15

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 de-ber-as20647 and it is hosted by CarrierColo / IPB GmbH in Berlin, Germany. 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Feedback about the new webinterface
by Klaus Darilion 20 Mar '15

20 Mar '15

Hi! First, thanks for the new web interface. I really like how you show the most important parts of the results, e.g. decoding the NSID for DNS measurements, and showing the traceroute with editable geolocation. Nevertheless I have some feedback: On https://atlas.ripe.net/probes/, when I search for probes matching "6939", I get the results in a list view of matching probes. In the list view, I can see the probe's ASN. But when the result set is small (e.g. 2 probes only), I do not get a "list view" but view with bigger "thumbnails", but missing the ASN information. Also viewing the details of a probe does not reveal the probes ASN. Similar with IP addresses. When viewing the results of a measurement on the map, if a click on a probe I get the probe's IP addresses. But when watching a probe's details I can not see the IP addresses of the probe. For me it is strange to get the probe's IPs and ASN not when watching the probe's details. This is quite some interesting info when selecting probes or when analyzing why the result from a certain probe was bad. Thanks Klaus

1 0