Stéphane Bortzmeyerv4 RIPE Atlas probes may be NanoPi NEO Plus2.
Probes as a virtual machine are still under evaluation.
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.
Just implemented "TCP ping" in my atlas-traceroute tool https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/commit/f5c4c181273f338e48705fbf7731a05b22b4e344 https://atlas.ripe.net/measurements/9716802/ https://labs.ripe.net/Members/stephane_bortzmeyer/using-ripe-atlas-to-debug-network-connectivity-problems #RIPEduca
New options (TCP, size, port), to do "TCP Ping" · RIPE-Atlas-Community/ripe-atlas-community-contrib@f5c4c18
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
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.
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
Shorter AS count with IPv6. Not much difference in RTT with IPv4. #RIPEduca