- ripe-atlas - mailman.ripe.net

Probe downtime notification
by Micha Bailey 26 Jan '16

26 Jan '16

I got an email 20 minutes ago telling me that my probe (#25346) is down, and apparently it's been down since 2016-01-24 15:11:10 UTC -- almost 24 hours. My settings are such that I should be getting an email within 15 minutes. Does anyone know why it's not emailing me right away? Has this happened to anyone else?

2 1

probe tagged as "Hardware problem suspected"
by sarah.wassermann＠student.ulg.ac.be 25 Jan '16

25 Jan '16

Hi, My probe (probeID: 24102) got tagged as "Hardware problem suspected" 2 weeks ago (and has also been disconnected since 2 weeks) and I am unable to bring it back to life again... (I am not an expert regarding hardware problems, so I will not be able to address the issue; restarting the router and plugging it out/back in didn't help). This probe behaved a bit strangely since the beginning: it disconnected itself for a few minutes per day without any reason, but I didn't pay much attention to that. Unfortunately, I need credits to conduct my research. Is it possible to order a new probe and to send this probe to RIPE? Maybe they can fix the problem and send the probe to someone who is interested in hosting a one? Thanks! Sarah Wassermann

3 6

Possible changes to the V1 REST API
by Chris Amin 22 Jan '16

22 Jan '16

Dear RIPE Atlas users, Over the past few days we have been making some changes behind the scenes in preparation for an upcoming version of the RIPE Atlas REST API. We identified and resolved several problems that these changes caused to the existing version of the API. The problems have now been fixed and you should not notice anything different with the existing API. If you continue to see anything strange, do please let us know. Kind regards, Chris Amin RIPE NCC

1 0

Display issues on the RIPE Atlas measurements listing
by Chris Amin 20 Jan '16

20 Jan '16

Dear RIPE Atlas users, Some of you may be noticing issues displaying measurements on the RIPE Atlas UI if you look at Public measurements or have lots of measurements of your own. We're currently working on this issue and apologise for any inconvenience caused. Kind regards, Chris Amin RIPE NCC

1 1

RIPE Atlas webinar recording and new dates
by Lia Hestina 18 Jan '16

18 Jan '16

Dear colleagues, We are happy to let you know that a recording of the Advance RIPE Atlas Usage webinar is now available on YouTube: https://www.youtube.com/watch?v=oJMFGuM0kMo <https://www.youtube.com/watch?v=oJMFGuM0kMo> <https://www.youtube.com/watch?v=oJMFGuM0kMo <https://www.youtube.com/watch?v=oJMFGuM0kMo>> If you would like to participate in a live webinar, we have two sessions available on the following dates: February 9 2016 March 17 2016 The Advanced RIPE Atlas Usage webinar teaches network operators how to use RIPE Atlas to monitor and troubleshoot their own networks. Learn more about the webinar and the necessary prerequisites: https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a… <https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a…><https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a… <https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a…>> RIPE NCC members can register online at: https://lirportal.ripe.net/training/register/courseCode/WEB20150046 <https://lirportal.ripe.net/training/register/courseCode/WEB20150046><https://lirportal.ripe.net/training/register/courseCode/WEB20150046 <https://lirportal.ripe.net/training/register/courseCode/WEB20150046>> Non-members can email training(a)ripe.net <mailto:training@ripe.net> <mailto:training@ripe.net <mailto:training@ripe.net>> and be manually registered. Kind regards, RIPE Atlas Team

1 0

Error on multi-probe measurement creation
by Matt Calder 15 Jan '16

15 Jan '16

Starting on Jan 6th, I started getting this error when creating new measurements. "Your selection of probes contains at least one probe that is unavailable. Error 104." These measurements had been running with no issues for the last year. I tried checking through the API that all probe's status' are Connected and are Public but it doesn't seem to make a difference. I am specifying a list of specific probes to be used which is needed for the specific experiment. Small number of probes like 1, 2, or 3 usually work. Larger numbers like 10 - 75, work occasionally. 300 - 400 probes per measurement never seem to work. Appreciate any help. Matt

1 1

What is 'iwantbcp38compliancetesting' user tag?
by Geert Jan de Groot 13 Jan '16

13 Jan '16

When revisiting the settings of my probe, I found this 'iwantbcp38compliancetesting' user tag. I know what BCP38 is, but what is the meaning of the tag? Is it a poll? Geert Jan

8 11

integrity checks for the Atlas software?
by Wilfried Woeber 12 Jan '16

12 Jan '16

While thinking about options or mechanisms to make virtual probes "tamper-proof" I had this question coming up: Is the probe software capable to "verify" (check-sum or digital sig) the bootstrap kit and then, during run-time, verify that the code in memory is still genuine? Thanks, Wilfried

6 5

Atlas probe offline
by Steve Hill 11 Jan '16

11 Jan '16

My Atlas probe (ID 14587) has been showing as offline since December 16th. I can see DHCP requests/replies, it ARPs for the gateway and I can see DNS requests and pings from the probe, and successful replies to all of this traffic being sent back to the probe. e.g.: 12:13:38.790096 IP 192.168.0.115.35404 > 217.146.115.154.53: 2+ AAAA? ctr-nue15.atlas.ripe.net. (42) 12:13:38.797337 IP 217.146.115.154.53 > 192.168.0.115.35404: 2 1/6/12 AAAA 2a01:4f8:120:14ee::2 (482) 12:13:38.798179 IP 192.168.0.115.57785 > 217.146.115.154.53: 3+ A? ctr-nue15.atlas.ripe.net. (42) 12:13:38.799649 IP 217.146.115.154.53 > 192.168.0.115.57785: 3 1/6/12 A 78.46.87.51 (470) 12:14:58.990977 IP 192.168.0.115.37934 > 217.146.115.154.53: 2+ AAAA? IUSB-READONLY.U36.M6466B3B0EC98.sos.atlas.ripe.net. (68) 12:14:59.060132 IP 217.146.115.154.53 > 192.168.0.115.37934: 2 1/1/2 AAAA 2001:67c:2e8:11::c100:1337 (164) 12:14:59.060983 IP 192.168.0.115.57523 > 217.146.115.154.53: 3+ A? IUSB-READONLY.U36.M6466B3B0EC98.sos.atlas.ripe.net. (68) 12:14:59.114915 IP 217.146.115.154.53 > 192.168.0.115.57523: 3 1/1/2 A 193.0.19.55 (152) 12:14:59.115925 IP 192.168.0.115 > 193.0.19.55: ICMP echo request, id 954, seq 0, length 64 12:14:59.142586 IP 193.0.19.55 > 192.168.0.115: ICMP echo reply, id 954, seq 0, length 64 12:15:00.116800 IP 192.168.0.115 > 193.0.19.55: ICMP echo request, id 954, seq 1, length 64 12:15:00.143773 IP 193.0.19.55 > 192.168.0.115: ICMP echo reply, id 954, seq 1, length 64 I can't see any other IPv4 traffic, but I do see IPv6 HTTPS traffic. I'm not sure where to go next with figuring out why the probe seems to have vanished. Any ideas would be greatly appreciated. Many thanks. -- - Steve

6 8

Examination of ARM based Atlas telemetry nodes
by Michael Schloh von Bennewitz 10 Jan '16

10 Jan '16

Hello developers, I'm scheduled to talk at the forthcoming MINIX conference, and was hoping to have the chance to examine your ARM based Atlas telemetry system. I only know of the Raspberry Pi devices loaned to the Tor project, and this could be relevant to my IoT work (leveraging IPv6 and ARM.) Andrew Tanenbaum recommended I write to Philip, is he here? Cheers, Michael -- Michael Schloh von Bennewitz Software Development Engineer Europalab Networks R&D, Munich Office: +49(89)44239885 UTC+2 Mobile: Same as 'Office' VoIP: sips:michael@schloh.com Web: http://michael.schloh.com/

3 2