- ripe-atlas - mailman.ripe.net

[Training] Launching RIPE NCC::Educa - Online Learning Event
by Sandra Bras 04 Sep '17

04 Sep '17

Dear colleagues, The RIPE NCC has a new way to dive deep into a topic without having to travel or leave your desk. RIPE NCC::Educa are free, online learning events that bring industry experts together to share insight, expertise and best practice with those that want more in-depth knowledge on a particular subject. Our first event focuses on RIPE Atlas on Thursday, 5 October from 8:00 - 13:00 UTC. Reserve your place here: https://www.ripe.net/support/training/ripe-ncc-educa <https://www.ripe.net/support/training/ripe-ncc-educa> You can join us for one session, multiple sessions or the full programme. We’re updating the agenda constantly, so be sure to check here for the latest additions: https://www.ripe.net/support/training/ripe-ncc-educa/agenda <https://www.ripe.net/support/training/ripe-ncc-educa/agenda> For more information on RIPE NCC::Educa, check out our RIPE Labs article: https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa <https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa> If you have any questions, please get in touch with us: <e-learning(a)ripe.net <mailto:e-learning@ripe.net>> Warm regards, Sandra Brás E-Learning Program Manager RIPE NCC

1 0

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

Probe recovery does not work
by Gil Bahat 27 Jul '17

27 Jul '17

Hi, I've finally managed to get a few USB drives to recover at least a few of my probes (I've spread about 3 dozen and only 2 are still online). But the stated recovery procedure does not work for me, with brand new 8GB keys. Is there any good way to see what's really going on with the recovery? the probes register themselves with the right addresses so I know connectivity and DHCP is ok, and yet they never recover. can the dhcp firmware be modified to try more aggressive recovery or better reporting of its state? Regards, Gil

1 0

Wifi measurements?
by Hank Nussbacher 24 Jul '17

24 Jul '17

When I start a new measurement, in addition to the standard measurements like ping and traceroute, I see a "wifi" measurement that appears for about 2 seconds at the end of the list and then auto-disappears. See attached screenshot. Explanations? Thanks, Hank

2 1

New on RIPE Labs: The Next Generation of RIPE Atlas Anchors
by Alun Davies 21 Jul '17

21 Jul '17

Dear Colleagues, The RIPE NCC is in the process of testing hardware for the next generation of RIPE Atlas anchors. Here’s a detailed overview of the process: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas… Best regards, Alun Davies RIPE NCC

5 4

NSID option on the RIPE Atlas SOA measurements of the root servers
by Chris Amin 20 Jul '17

20 Jul '17

Dear colleagues, RIPE Atlas is currently running a series of DNS SOA built-in measurements* towards all of the root servers from all probes. During the recent DNS measurements hackathon** it became apparent that for some use cases it would be useful to have SOA queries from all probes with the NSID EDNS option set, in order to be able to match up responses with the particular responding instances in an anycasted (or load balanced) setup. We would like to ask for feedback on two alternative options for implementing this change. They are: 1) Enable the NSID option for the existing built-in measurements towards the nine root servers which support it. 2) Start a new set of built-in measurements towards the nine root servers which support NSID. The advantages of option (1) are that it will be possible to compare and contrast the two sets of results, and that historical data for the existing built-ins will remain consistent with the current results. A very simple analysis shows that there is no overall increase in query error rates through enabling NSID, but there are bound to be individual marginal cases where queries fail or produce different results with NSID set but succeed without it. The advantages of option (2) are that there will be no increase in result storage usage -- the current IPv4+IPv6 UDP SOA built-ins towards the nine supporting root servers adds up to about 80 results per second (~1.5% of the total results in the system). This could potentially be mitigated by reducing the frequency for these new measurements, but perhaps more important than the slightly increased load is the potential user confusion caused by generating and providing two very similar sets of measurements. Please let us know if you have any preference for which way we go on this, particularly if you have a (current or future) use case for this kind of data. Kind regards, Chris Amin RIPE NCC * https://atlas.ripe.net/docs/built-in/ ** https://labs.ripe.net/Members/becha/results-dns-measurements-hackathon

1 0

Update on the anchoring measurements change
by Johan ter Beest 20 Jul '17

20 Jul '17

Dear all, As described in the labs article here: https://labs.ripe.net/Members/alun_davies/balancing-act we have split the anchoring measurements. We are currently in the process of adding more probes to the new 'probe' anchoring measurements. We expect this to be completed by the end of this week. Please let us know if you notice anything out of the ordinary. Kind regards, Johan ter Beest RIPE Atlas Team

1 0

Link aggregation for anchors?
by Tore Anderson 20 Jul '17

20 Jul '17

Hi, I was wondering if it is possible to connect our anchor in a fault tolerant fashion using 802.3ad link aggregation? This would allow us to perform serialised maintenance on the upstream switches without ever offlining the anchor. Tore

4 6

Trace and Ping measurements fail on Probe 15861
by ripe＠brite.cz 18 Jul '17

18 Jul '17

Hi team, recently I'm not able to run measurements on probe 15861 I am hosting at home. When I create a measurement with only this probe, it ends up in Failed status [measurements 9193416 9193417 9199824 for example]. When there is multiple probes in the measurement, probe 15861 ends up showing "No recent report available" [9193406 9192883]. Otherwise the probe has been online and does not show any anomalies. Any idea? Thank you Jiri

1 0

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