August 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

Infrastructure upgrades
by Robert Kisteleki 06 Sep '17

06 Sep '17

Dear all, Yesterday we began infrastructure (OS) upgrades on our controllers. As a consequence each probe will be disconnected for an hour or two. This can trigger notifications, if you have that configured to a sensitive enough setting. Regards, Robert Kisteleki RIPE NCC

3 4

Sharing Credits seems broken .....
by Barry Raveendran Greene 24 Aug '17

24 Aug '17

Hi Team, We have a problem with the sharing credits. I’ve got plenty of credits on my account. I’ve granted access to my colleague (Jim Gilbert) and a test group account (atlas-network(a)akamai.com). Just to be clear, it states: Sharing Access - If you don’t want to set limits on the number of credits you share, you can also allow other RIPE Atlas users to use your credits directly for their own measurements. Select the “Share Access” tab on your credits page and enter the RIPE Atlas users you want to give access to. Users who have been given access to others’ credits will be able to choose whose account to charge when they create a new measurement from a drop-down menu. This option can also be set via the measurement API. A running measurement can be stopped by both you and the person with access to your credits. If you decide to stop giving someone else access to your credits, any measurements they have running will start using their own credits instead. This means I should be able to log into atlas-network(a)akamai.com select “bgreene(a)senki.xn--org-9o0a and create/run test. Correct???? This is what I get: What are we missing? Barry

2 2

DNS results visualisation
by Dave . 22 Aug '17

22 Aug '17

Hi, For the traceroute results there is a icon at the right side where you can get the complete traceroute. (View Latest Result) This is beautifully presented. Could we please have a similar icon for DNS results? Thanks, Dave Boonstra

2 2

measurement UI on 12hour clock?
by Rene Wilhelm 22 Aug '17

22 Aug '17

See attached screenshot. I created a couple of measurements which were to start at 16:05 local time, 14:05 UTC. The measurement page https://atlas.ripe.net/measurements however states a start time of 22-08-2017 02:05 UTC which is of course 12 hours in the past and had me worried for a bit I made a mistake filling in the form. Can this be fixed? it is confusing and looks a bit clumsy :) -- Rene

2 1

[rfc-editor@rfc-editor.org: RFC 8193 on Information Model for Large-Scale Measurement Platforms (LMAPs)]
by Stephane Bortzmeyer 22 Aug '17

22 Aug '17

This recent RFC on the data model for Internet measurements platform is of course of interest for RIPE Atlas. Note that their model separates controller and collector, which are one in Atlas.

1 0

New on RIPE Labs: Processing RIPE Atlas Results with jq
by Mirjam Kuehne 21 Aug '17

21 Aug '17

Dear colleagues, Please find this new article by Stephane Bortzmeyer on RIPE Labs: Processing RIPE Atlas Results with jq https://labs.ripe.net/Members/stephane_bortzmeyer/processing-ripe-atlas-res… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Notify time setting does not work
by Marat Khalili 18 Aug '17

18 Aug '17

Probes have very handy feature of sending a notification when the probe is disconnected. I have mine set to 10 minutes, however last two such notifications only arrived 30 minutes after the probe was disconnected. Probe #26656 if that's important. One would think that probe itself was slow to react, but last time I monitored outage from the very beginning and the probe's page correctly showed "Disconnected for: 1 minute" and so on. Neither it is a case of slow email arrival, since according to Received header in the email it was indeed received from worker1.atlas.ripe.net 30+ minutes after disconnection time mentioned in the email body. Can it be that "Notify time" setting just doesn't work and some default value of 30 minutes is used? -- With Best Regards, Marat Khalili

4 7

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

Updated RIPE Atlas measurements listing page
by Massimo Candela 09 Aug '17

09 Aug '17

Dear RIPE Atlas users, With the increasing number of measurements supported by RIPE Atlas, the measurement listing page [1] was slowing down. Today we deployed a new release with improved performance and functionality. The new page contains a re-arrangement of the tabs, allowing the user to more easily access the types of measurement they are interested in. The searching has also been improved, allowing more precise filtering of the measurements. If you experience any issues, try to refresh the cache for the page. And of course, let us know if you have any feedback about this change. Best regards, Massimo Candela Software Engineer - RIPE Atlas project [1] https://atlas.ripe.net/measurements/ <https://atlas.ripe.net/measurements/>

1 0

Test, please ignore
by Robert Kisteleki 08 Aug '17

08 Aug '17

1 0

Update to RIPE Atlas Anchors Article
by Michela Galante 08 Aug '17

08 Aug '17

Dear colleagues, We just published an update to the RIPE Labs article “The Next Generation of RIPE Atlas Anchors”. You can read it here: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas… Best regards, Michela Galante RIPE NCC

2 3

Join RIPE NCC Hackathon Version 6, 4-5. November, Copenhagen, Denmark
by Vesna Manojlovic 08 Aug '17

08 Aug '17

Dear colleagues, The sixth RIPE NCC hackathon will take place on Saturday and Sunday, 4-5 November 2017 in Copenhagen, Denmark. The topic is: IPv6! We're looking for creative thinkers: front-end developers, UI designers, network operators, researchers, hackers and other enthusiastic coders, to help us develop new tools that would enable deployment of IPv6 and visualizations based on IPv6 measurements data. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://atlas.ripe.net/hackathon/version6/#!application-form *The application deadline is 9.9.* (9th September) We look forward to seeing you there! Find out more in this RIPE Labs article: https://labs.ripe.net/Members/becha/join-the-ripe-ncc-hackathon-version-6 Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

SOS History empty since 2017-07-20
by Christian Schrötter 01 Aug '17

01 Aug '17

Hi, the last entry in my SOS History is from 2017-07-19, see screenshot [1]. My probe is still connected and working, but there should be two items per day at minimum, for each reconnect of my DSL connection after 24 hours. Looks like something is broken at the Atlas system. Could someone confirm this bug? -- Regards, Christian [1]: https://happytec.at/r/Xfaab

2 2