- ripe-atlas - mailman.ripe.net

Failure Rate on Atlas Probes
by Jonathan Brewer 23 Apr '16

23 Apr '16

Hi All, What's the known failure rate of Atlas probes, and the mean time before failure? At a guess 20% or more of the probes I've been working with have failed within their first year of deployment. Sometimes they come back with a power cycle, sometimes they don't. Regards, Jon

1 0

Probe not received
by rgnr＠riseup.net 22 Apr '16

22 Apr '16

Hey, as the subject says. It's been 4 weeks now and nothing has arrived. Any clues what to do? regards Bernd

2 1

Led WPS / RESET
by Anthony 22 Apr '16

22 Apr '16

Hello everyone, I had a power outage, so I had to reboot my box and my probe, but now the LED button "WPS / RESET" lights is this normal? Before it off extinct. thank you in advance

2 4

New on RIPE Labs: Looking at IXPs in Berlin with RIPE Atlas
by Vesna Manojlovic 21 Apr '16

21 Apr '16

Dear colleagues, The IXP country jedi tool described in earlier RIPE Labs articles, can now also be used to analyse the situation in a specific city. This time we look at Berlin, Germany: https://labs.ripe.net/Members/mirjam/using-ripe-atlas-to-look-at-ixps-in-be… Regards, Vesna

1 0

Probe status / self-help
by Robert Kisteleki 20 Apr '16

20 Apr '16

Dear All, Today we released a new feature intended to help the probe hosts detecting, understanding and fixing various issued related to probes. You should be able to see a new "Status" tab on your probe page. This is where we explain various conditions, such as USB problems, non-working IPv6 or DNS resolutions quirks. Please note that this bit is in early stages (officially labeled as beta). We believe it works in general, however for now it only explains various system tags that mark error conditions. It will have more features in the future. It is also intended to be a place where we can add features that explain, for example, "your probe behaves differently than the rest" or "path MTU issues detected" or such. We think this will be a useful feature to hosts. Let us know if you have specific suggestions for improvement. Regards, Robert Kisteleki RIPE NCC

3 2

*-capable ≠ *-works + *-doesnt-work
by Bajpai, Vaibhav 20 Apr '16

20 Apr '16

Hello, I am looking at the probe API data for connected probes (status = 1) for day = 20160418 system-ipv6-capable = 3556 system-ipv6-works = 2995 system-ipv6-doesnt-work = 710 Why is system-ipv6-works + system-ipv6-doesnt-work > system-ipv6-capable? system-ipv4-capable = 9336 system-ipv4-works = 9187 system-ipv4-doesnt-work = 67 Why is system-ipv4-works + system-ipv4-doesnt-work < system-ipv4-capable? Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

2 2

Question
by Anthony 19 Apr '16

19 Apr '16

Hello, I would have wanted to know if my graphs probe appears well is how well does the measures not? For you everything is ok or not? : https://atlas.ripe.net/probes/27379/ thank you in advance

2 2

RIPE Atlas CLI Toolset now available on NLNOG RING
by Vesna Manojlovic 19 Apr '16

19 Apr '16

Dear colleagues, in the spirit of cooperation between the monitoring & measuring platforms, I am happy to announce: RIPE Atlas CLI Toolset have been installed on RING! If you are already participating in NLNOG RING, now you can use RIPE Atlas CLI Toolset for "quick & dirty" access to RIPE Atlas measurements & probes. More info about RING: https://ring.nlnog.net RING nodes are also available as targets through RIPE Atlas web interface for measurements creation: https://atlas.ripe.net/targets/ringnodes/list/ https://atlas.ripe.net/targets/ringnodes/map/ Regards, Vesna Reminder about CLI tools: Source: https://github.com/RIPE-NCC/ripe-atlas-tools/ Documentation: https://ripe-atlas-tools.readthedocs.org/ In addition to "raw install", tools are also packaged in many distros: OpenBSD, FreeBSD, Gentoo, Arch, Debian and Ubuntu (in progress: Fedora, Windows). Examples of usage of RIPE Atlas CLI tools on RING: ripe@ripe01:~$ ripe-atlas report 1001 --probes 1 20 bytes from probe #1 212.238.160.244 to 193.0.14.129 (193.0.14.129): ttl=59 times:6.658, 6.591, 6.298, ripe@ripe01:~$ ripe-atlas measurements --af 6 --status ongoing --limit 15 --search nlnog Filters: Search: nlnog Af: 6 Status in: (2,) Id Type Description Status ================================================================================ 1027844 traceroute Jump Ongoing 1027846 traceroute Clara DE Ongoing 1037103 ping tenet01.ring.nlnog.net Ongoing 1404594 ping RedpillLinpro-v6 Ongoing 1596748 ping world4you01.ring.nlnog.net Ongoing 1688325 ping ping6 on amazon03 Ongoing 3678270 traceroute Traceroute measurement to bluezonejordan01 Ongoing ================================================================================ Showing 7 of 7 total measurements ripe@ripe01:~$ ripe-atlas configure --setauthorisation.create=7b4c-xxxx ripe@ripe01:~$ ripe-atlas measure ping --target ping.xs4all.nl Looking good! Your measurement was created and details about it can be found here: https://atlas.ripe.net/measurements/3671547/ Connecting to stream... 48 bytes from probe #6174 217.10.140.74 to 194.109.6.8 (194.109.6.8): ttl=56 times:8.849, 8.781, 8.78, 48 bytes from probe #26941 88.85.47.152 to 194.109.6.8 (194.109.6.8): ttl=55 times:74.372, 74.487, 74.748, 48 bytes from probe #24596 176.144.180.224 to 194.109.6.8 (194.109.6.8): ttl=57 times:45.418, 45.249, 45.5, 48 bytes from probe #6187 196.10.54.135 to 194.109.6.8 (194.109.6.8): ttl=56 times:155.65, 155.58, 155.668, 48 bytes from probe #3207 37.49.102.93 to 194.109.6.8 (194.109.6.8): ttl=50 times:24.4, 27.627, 21.95, 48 bytes from probe #6186 82.195.72.11 to 194.109.6.8 (194.109.6.8): ttl=58 times:7.087, 7.101, 7.052, ... Read more about it on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-cli-tool…

1 0

API filtering for looking at measurements?
by Baptiste Jonglez 18 Apr '16

18 Apr '16

Hi, I would like to find measurements matching some specific conditions, so I tried to use the measurement API documented here: https://atlas.ripe.net/docs/rest/ However, filters don't seem to have the intended effect. For instance, I tried to restrict to a specific range of starting time: https://atlas.ripe.net/api/v1/measurement/?start_time__gte=1443654000&start… but looking at the first result (measurement ID 1411440), its start time is 1564618500, which is way outside of the requested range. Similarly when filtering by type: https://atlas.ripe.net/api/v1/measurement/?type=2 type=2 is supposed to be IPv4 traceroute, but the first result is measurement ID 1001, which is an IPv4 ping. Am I using the API incorrectly, or is there a bug somewhere? Thanks, Baptiste

2 2

Open ports?
by Anthony 15 Apr '16

15 Apr '16

Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open? How to know if everything is ok? Sorry for my English, thank you in advance

4 5