June 2017 - ripe-atlas - mailman.ripe.net

Error: Only anchors may be targeted.
by Mozafary Mohammad 28 Jun '18

28 Jun '18

Hello I've got "Only anchors may be targeted." on HTTP measurement creation.Any body can advise what the problem is? Thanks

8 9

New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives
by Mirjam Kuehne 02 Mar '18

02 Mar '18

Dear colleagues, In this article we present a new way to access the dataset on the RIPE Atlas platform. Instead of fetching individual results from measurements using the available APIs, you can now download files containing public measurements for a given day. Please find more details on RIPE Labs: https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data… Kind regards, Mirjam Kühne RIPE NCC

9 12

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 09 Oct '17

09 Oct '17

Dear colleagues, We wanted to update the community and let you know that we plan to start work on the proposed experiment with WiFi measurements in mid-2016. As we communicated in a recent RIPE Labs article, we will work with GÉANT as a test partner to learn more about the operational effects of introducing WiFi measurements to the RIPE Atlas system, in addition to the benefits we believe this could provide for the entire RIPE Atlas community. Please see the article for more details if you are interested: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… We will continue to update you once we’ve begun work on this plan, and we welcome your comments in the meantime. Regards, Robert Kisteleki RIPE NCC

3 3

Your probe is currently disconnected
by Conrad Kostecki 15 Aug '17

15 Aug '17

Hi! I've applied for an Atlas probe v3 and got one via postage. So, I've connected the probe to my network. I can see in my DNSMasq logs, that the probe gets successfully an IP address. It can be pinged without any problems. But that's all. Even after 24 hours it's still reported not connected. I can see multiple LEDs: 1 (power): on 2: off 3: slow blink 4: fast blink 5 (button): on I can't find that in the FAQ, the LEDs should light different. The FAQ also did mention to try first without USB and insert USB later. Or try to replace the USB. Both cases did not help. If I connect my ThinkPad instead the probe with the same network connection (cable and port), it can access the internet just fine without any problems.. I've no clou, what could be wrong. Any ideas? Thanks! Conrad Viele Grüße Conrad Kostecki

7 9

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

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

Improvements to the RIPE Atlas measurement creation form
by Chris Amin 15 Jun '17

15 Jun '17

Dear all, We’ve made some changes to the interface for creating measurements on the RIPE Atlas website (https://atlas.ripe.net/measurements/form/) that will make it both faster and more responsive. Users should also see similar improvements in the user interface for monitoring and configuring domains with DomainMON (https://atlas.ripe.net/domainmon/). The changes were made possible by switching to the public measurement API (https://atlas.ripe.net/docs/api/v2/manual/). Concurrently with this, we also improved the error reporting in the API to make it easier to find out the cause of errors. This API change is backwards compatible and is documented in the API manual (https://atlas.ripe.net/docs/api/v2/manual/overview/error_messages.html). Whilst we do not expect the transition to cause any issues, we kindly ask that users let us know if they experience anything out of the ordinary that might be related to the change. Best regards, Chris Amin RIPE NCC

1 0

Firmware Update for RIPE Atlas V1 and V2 Probes
by Alun Davies 09 Jun '17

09 Jun '17

Dear all, We’re currently in the process of deploying a new firmware update for RIPE Atlas V1 and V2 probes. The update provides a fix for a bug that caused around 15% of RIPE Atlas V1 probes to disconnect. As of the time of writing, the update is at approximately 60% deployment. If you’ve been unable to reconnect your RIPE Atlas V1 probe, you can return it to the following address to be fixed. If you’d like the probe to be returned to you afterwards, please let us know. Alternatively, we’d encourage you to apply for a V3 probe. RIPE NCC P.O. Box 10096 1001EB Amsterdam The Netherlands We’d like to take this opportunity to thank all probe hosts for your ongoing efforts in supporting RIPE Atlas. Cheers, Alun Davies RIPE NCC

1 0

Anchors as target hosts for SLA
by Antonio Prado 06 Jun '17

06 Jun '17

hi, do you think could be a good idea to use Ripe Atlas Anchors as target hosts for measuring respect of SLA terms of an Internet transit? SLA example This Internet transit should meet the following criteria: average round trip delay (echo request, echo reply) toward $NEAREST_ATLAS_ANCHOR should be less than 100ms on a 10k packets stream of pings; packet loss equal or less than 0.02% pros, cons, recommendations? thank you -- antonio

3 3