#RIPEduca starts in less than one hour https://www.ripe.net/support/training/ripe-ncc-educa Today, RIPE Atlas probes!
One last coffee and I stand ready.
#RIPEduca starts in less than one hour https://www.ripe.net/support/training/ripe-ncc-educa Today, RIPE Atlas probes!
One last coffee and I stand ready.
Reminder: RIPE Atlas probes are a distributed network of probes that *you* can use to test Internet connectivity from many (10 000) vantage points https://atlas.ripe.net/
A must for any serious Internet professional.
These probes can do several sort of measurements, requested by users (you and me) : ICMP echo (ping), traceroute (UDP and ICMP), DNS, etc. Here, the current measurements: https://atlas.ripe.net/measurements/ #RIPEduca
RIPE Atlas is therefore a nice botnet.
Now, RIPE Atlas probes and Internet Exchange Points, by Willem Toorop and Emile Aben.
"We will start with the first presentation" #captainObvious
A study of Internet connectivity in Canada
The Canada interconnectivity survey was done by analysis *existing* RIPE Atlas measurements (by default, measurement results are public).
Among the questions: how much of canadian traffic stays inside Canada? Between unicast machines (gov. Web servers for instabce) hosted in Canada? Between a probe in Canada and a anycast DNS server which has instances in Canada?
Usual problems of Internet measurements: traceroute with non-responding routers, routers replying with RFC 1918 (private) IP addresses, geolocation inperfect...
Ping @angristan about the ability of the US to shut down the Internet: some Canada traffic goes through the US.
Result: 64 % of "canadian" traceroutes go through the US. (And these traceroute are often faster, which may be the reason: international links are upgraded more often; another reason is the lack of peering in the country)
Only 29 % of canadian governement sites are hosted in Canada. (And traceroute to them often go through the US.)
Emile Aben presents "IXP Jedi", a measurement of the actual use of Internet Exchange Points (like the France-IX) through RIPE Atlas measurements. Do they really "keep local traffic local"? [Insert picture of a very smiling user]
Example of #Finland: the most common path between two finlandeses probes is inside the country but not crossing an IXP. A minority goes through an IXP.
Example of #France: some FR-FR paths go through the US (and many go to another of the Five Eyes, such as GB) [Remember that Orange does not peer at a public Exchange Point in France]
Christopher Amin on RIPE Atlas API https://atlas.ripe.net/docs/api/v2/
"Everything that you post is JSON. Everything that you get is JSON."
"Works in any language"
Massimo Candela about the other RIPE Atlas API (the streaming one) and how to use it.
Vesna Manojlovic now speaking for webmasters: "measuring reachability of your Web server" with RIPE Atlas #RIPEduca
Atlas was more focused on layer 3. But users requested L7 measurements.
Ping @Natouille, @aeris and the others at #ParisWeb
Limitations of HTTP measurements: only towards RIPE Anchors, partly for ethical reasons (forbidden Web sites) partly to avoid LOIC-type dDoS.
The trick: "TCP ping" with the traceroute measurements towards port 80, packet size zero.
ripe-atlas-community-contrib - Repository for links towards tools written during hackathons, and a collection of contributions by the community of the RIPE Atlas visualizations, tools for analysing measurements data and other scripts
Now, Robert Kisteleki is closing the #RIPEduca event.
10 200 RIPE Atlas probes, 3 600 AS covered in IPv4, 1 350 in IPv6. 450 megabytes of measurements collected pe day.
There are still 600 v1 probes connected. uClinux
v3 uses OpenWRT and Busybox. But it had a lot of USB keys issues.
v4 RIPE Atlas probes may be NanoPi NEO Plus2.
Probes as a virtual machine are still under evaluation.