- ripe-atlas - mailman.ripe.net

New RIPE Atlas Measurement Options
by Alun Davies 17 Jul '17

17 Jul '17

Dear all, The RIPE Atlas team have added a number of new measurement options on RIPE Atlas. Here’s an overview of the changes: DNS measurements timeout: allows the user to specify a custom timeout in milliseconds after which probes will stop waiting for a response from the DNS server use_macros: allows the use of special macro strings in the "query_argument" field, to create unique or easily distinguishable queries. The allowed macros are: $p the (integer) ID of the probe carrying out the measurement $r a random 16-digit hexadecimal string $t a Unix timestamp of the time that the probe carries out the DNS query SSLcert measurements hostname: specifies a hostname to send as a Server Name Indication (SNI), which is necessary for web servers which host multiple TLS domains on the same IP address. Ping measurements include_probe_id: include the probe ID as an ASCII string within the payload of ping measurements. Note: this is included in addition to other payload data. The changes are all included in the RIPE Atlas API reference: https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li… <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li…> If you have any questions whatsoever about the new measurement options, do let us know. As always, we welcome suggestions for new features from RIPE Atlas users. Best regards, Alun Davies RIPE NCC Communications Department

1 0

Caching issues on the latest call
by Johan ter Beest 13 Jul '17

13 Jul '17

Dear all, Today we became aware of some caching issues on the latest API call (https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Latest_GET). In certain corner cases it was possible that an incomplete set of results for a logged-in user was cached for up to 24 hours. This did not apply to non logged-in users as the results are not cached in that case. A fix for this issue has been deployed and going forward the latest call will have a 1 minute cache regardless of whether the user is logged in or not. As caching is always tricky, we kindly ask that users will let us know if they experience anything out of the ordinary that might be related to this change. Kind regards, Johan ter Beest RIPE Atlas Team

1 0

half dead v1 probe ?
by Matthieu Herrb 13 Jul '17

13 Jul '17

Hi, Here at Tetaneutral.net we're hosting a V1 Atlas probe since 2012 or so. A few weeks ago it started beeing marked as unconnected on the ripe atlas page : https://atlas.ripe.net/probes/523/ Since it's a v1 probe, I can only power cycle it to try to reconnect it, which I've done a number of times now, without success. It's still answering to ping requests, both on its v4 and v6 addresses and I can see some traceroute-like trafic going out of it. It's marked as "firewall problems suspected", but we don't do any firewalling on it. On IPv4 it's on a 1:1 NAT, all ports are open and forwarded in both directions, and on V6 it's routed without any filtering. Also we haven't changed anything on our infrastructure around the time it became disconnected. I'm starting to suspect a firmware upgrade problem as the one mentionned by Alun Davis in https://www.ripe.net/ripe/mail/archives/ripe-atlas/2017-June/003329.html Any suggestion before I send it back and ask for a new one ? Thanks in advance, -- Matthieu Herrb

3 2

Probe does not request IPv4 address via DHCP
by Stanish Stanishev 11 Jul '17

11 Jul '17

Hello, My probe(ID 16372) has disconnected from the Atlas network and in the Status I see USB flash corrupted. I did the troubleshooting - power off the probe, remove the USB, power on the probe, waited 10 mins, plugged brand new 4G USB. Several times with no success, So I decided to do a traffic capture of the uplink port where the probe is connected to. According to the capture the probe does not send DHCP requests. It sends only IPv6 traffic - Multicast Listener reports and Neighbor solicitation. Hence not getting IP address. I did several restarts - no change. Anybody has seen this issue before ? Any hints how to deal with such issue ? Thanks Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 9

New on RIPE Labs: Anchoring Measurements - Bringing Back the Balance
by Mirjam Kuehne 06 Jul '17

06 Jul '17

Dear colleagues, Please read on RIPE Labs how we're striking a balance between probes and anchors in RIPE Atlas anchoring measurements: https://labs.ripe.net/Members/alun_davies/balancing-act Kind regards, Mirjam Kühne RIPE NCC

1 0

[ripe-atlas-tools] Anyone had success with renderer aggregate_ping?
by Stephane Bortzmeyer 05 Jul '17

05 Jul '17

I cannot make the renderer aggregate_ping work: https://github.com/RIPE-NCC/ripe-atlas-tools/issues/186

1 0

New on RIPE Labs: Next Five Sponsored RIPE Atlas Anchors
by Mirjam Kuehne 04 Jul '17

04 Jul '17

Dear colleagues, The second phase of the RIPE NCC’s campaign to sponsor 15 RIPE Atlas anchors has been completed, with another five anchor hosts selected for sponsorship. We want to tell you about the new anchor hosts and also take a look at some related developments here at the RIPE NCC: https://labs.ripe.net/Members/alun_davies/next-five-sponsored-ripe-atlas-an… Kind regards, Mirjam Kühne RIPE NCC

1 0

Monthly probe report says it was down for the entire month
by James Andrewartha 03 Jul '17

03 Jul '17

Hi, I got my monthly probe report and oddly it says my probe was down for the entire month, rather than the 14d 6h 55m (47.63%) the website says. I've only just been able to reboot the probe (it didn't respond to ping at all), and it has come up with a new IP, but hasn't connected to the controller. Some things have updated with the new IP, eg p29530.probes.atlas.ripe.net but others like the local address are still showing the old IP. Should I try doing the recovery procedure? Thanks, James -------- Forwarded Message -------- Subject: Monthly probe report for CCGS Perth (#29530) Date: Sat, 1 Jul 2017 01:50:21 +0000 From: RIPE Atlas <no-reply(a)ripe.net> Reply-To: RIPE Atlas <no-reply(a)ripe.net> To: linuxadmin(a)ccgs.wa.edu.au Dear James Andrewartha, This is your monthly availability report for probe 29530 (CCGS Perth). Calculation interval : 2017-06-01 00:00:00 - 2017-07-01 00:00:00 Total Connected Time : 0d 00:00 Total Disconnected Time : 30d 00:00 Total Availability : 0.00% This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to receive reports about probe availability. If you would like to change this, or disable this reporting altogether, please go to https://atlas.ripe.net/probes/29530/, click the "Edit" button next to "Notifications", and use the form there to define what you want. Kind regards, RIPE Atlas Team

2 1

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
by mostafa shahdadi 21 Jun '17

21 Jun '17

Sent from my iPad

1 0

atlas feature suggestion
by Geert Jan de Groot 20 Jun '17

20 Jun '17

Hi, On the portal: > Notifications > Notify me at my registration address if this probe is down for more than 600 minutes. This doesn't seem to take into account that a probe may be dual-stacked (v4 and v6) and just one of these protocols may fail w/o the other one failing as well (this is a problem with my CPE, but I'm not touching that box until the temperature in the lab has dropped to sensible values) In any case, if v6 dies but v4 still works, the probe doesn't complain. Perhaps this should be flagged separately? How are we doing on testing silent v6-failures in general? Happy eyeballs make a lot of breakage invisible.. Geert Jan

1 0