- ripe-atlas - mailman.ripe.net

Software Probe version 5100
by Michel Stam 07 Oct '24

07 Oct '24

Dear colleagues, We’d like to inform you that a new version of the software probe has been released, version 5100. Please find the changes below: All platforms As of this version, the ripe-atlas-probe-measurements repository on GitHub is deprecated. Its code has been merged into the ripe-atlas-software-probe repository Package can now be built with arbitrary shell shebangs. Note that only OpenWRT ash and bash are officially supported Bug fixed where permissions are wrong when systemd is disabled (reported by César de Tassis Filho <ctassisf(a)gmail.com>) A new code signing key has been introduced. It only signs Debian packages currently, but will sign the RHEL packages in an upcoming release as well. The current RHEL key will then be deprecated. This release already supports code signed using the new key Software probes Streamlined deployment on RHEL CI/CD systemd unit ownership moved to probe and anchor packages Debian 11/12 x86_64 support added Support for OpenWRT software probes and the hardware probes v3, 4 and 5 will be added in a future release. If you run RHEL or Debian, we encourage you to upgrade to the latest version: https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Linux-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/RHEL8-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/RHEL9-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Debian… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Debian… Best regards, Michel Stam, RIPE Atlas development team

2 3

Some built-ins are not working anymore
by Ernst J. Oud 07 Oct '24

07 Oct '24

I guess due to the new controller infra, the built-ins measurements for: ctr-ewr01.atlas.ripe.net ctr-fnc01.atlas.ripe.net ctr-sin02.atlas.ripe.net are invalid now? They don’t produce data since October 1st it seems. Will the new controllers be included as built-ins? Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud

2 1

About the recent connection problems
by Robert Kisteleki 02 Oct '24

02 Oct '24

Dear colleagues, As many of you have noticed, we have been experiencing some technical issues with RIPE Atlas over the past few weeks. I would like to explain some of these in this email. Earlier this year, we began the process of migrating our infrastructure from our on-premise and co-located data centres to a cloud-based solution. Significant work has gone into rewriting code for multiple components and to renew the underlying infrastructure, to containerise and adapt it for the new cloud environment. In the process of this, we have encountered unforeseen bugs and bottlenecks. The RIPE Atlas team has been working to fix these issues as we find them. We are largely done with the migration of the controlling infrastructure so we hope to have a more stable system in the coming days. We are deploying new code and fixes fairly often to prevent these issues from arising, but it is possible that you might experience unexpected disconnects, but hopefully on a smaller scale than the past weeks. In the coming weeks, we will also begin the migration of the website (the user interface and the API). To clarify some questions that we heard on the list: - We will be looking for a solution to compensate credits for the missing connection times. - In the vast majority of cases, we don’t expect data loss when probes are not connected. The measurement results are delayed until the probes can reconnect and submit the results. - We apologise for the many connection and disconnection emails you might have received when your probe is disconnected. Please note that you can change your email notification preferences on your probe status page. I understand that many of you will want a more detailed explanation. We will be publishing an article on RIPE Labs, and we plan to present our work at the MAT Working Group session at RIPE 89. Regards, Robert Kisteleki RIPE NCC

1 1

Atlas UI update 2024-09-23
by Stephen Suess 23 Sep '24

23 Sep '24

Hello Atlas fans, We just released an update to the UI that includes: - NEW: Results ASNs visualisation in DNS measurement overview map - CHANGE: Anchor list improvements (status, search, sorting) - CHANGE: Ambassador Probe card now allows inline note editing In addition, we have some improvements to the new advanced search in the probes and measurements lists, and some other under the hood improvements. If you want to see the full list of what has changed, you can check the release notes here: https://atlas.ripe.net/docs/releases/website/2024-09-23.html As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

1 0

LACNIC42 IMWG call for presentation LAST DAYS!
by Elisa 19 Sep '24

19 Sep '24

Dear all, LACNIC 42 / LACNOG 2024 (7-11 October 2024, Asunción, Paraguay) is coming up and we will have a session for the Internet Measurements Working Group (IMWG)! We are looking for presentations on Internet measurements, network data collection, data analysis and tools. Please, submit your presentation proposal by sending an email to imwg-owner(a)listas.nog.lat We prefer talks of 15min. Include in your email: 1) a title; 2) a draft of the presentation; 3) a paragraph describing what you will talk about and why the topic is of interest for the community; 4) if you are planning to present in person or remotely. Thanks! Cheers, -- Elisa Peirano *Analista de Datos I+D* R&D Data Analyst /www.lacnic.net <http://www.lacnic.net> Latin American and Caribbean Internet Addresses Registry/

1 0

Not only are probes disconnecting…
by Ernst J. Oud 18 Sep '24

18 Sep '24

Current Atlas status shows a delay of over 16 hours. I created a measurement and no data is returned. It appears this is not a problem with only probes disconnecting… Ernst J. Oud

3 3

Auto reconnect?
by Ernst J. Oud 17 Sep '24

17 Sep '24

Is it true that probes will always automatically reconnect? Probe 60200 was down for a total f 17 hours (with a short reconnect of some minutes in the middle of that period). I just did a power recycle and it immediately reconnected. All my probes have reconnected now. Thanks for resolving this. Regards, Ernst J. Oud

1 0

Re: Again probe disconnects on ctr-dub-hw01 (Robert Kisteleki)
by ripe＠nurfuerspam.de 17 Sep '24

17 Sep '24

> they will > continue to run the defined measurements, reconnect when they can, and > send in all the stored results Actually, that seems not entirely true, at least not in all cases. That is how I mostly notice that one of my probes (likely) had a disconnect lasting more than a few minutes (but not enough to get a notification mail), because gaps in the RIPEstat graphs are noticeably visible as vertical gray bars without data points, or short gaps in an otherwise continuous line (at the typical graph resolution for a relevant measurement).

1 0

Again probe disconnects on ctr-dub-hw01
by Ernst J. Oud 17 Sep '24

17 Sep '24

Today my probes 60200 and 61071 experience several disconnects of upto an hour, both on controller ctr-dub-hw01. It appears this supposedly fixed disfunction has not been completely fixed. Regards, Ernst J. Oud

8 10

Subject-line in (dis)connect mails
by Marco Davids (Private) 11 Sep '24

11 Sep '24

Dear Atlas folks, I was wondering if it is possible to bring dis- and reconnect messages of RIPE Atlas probes more in line with each other. The disconnect mail has a subject like this: "Probe ID is disconnected (Name (ISP))" The reconnect mail has this: "Your RIPE Atlas Probe (ID: XXX) has reconnected" For me this is a bit confusing. When I sort my inbox alphabetically on subject, it would be really nice if the messages are grouped close together, which currently is not the case. It would helpful to me if this could be improved, by adjusting the specific text in the subject a bit. Thanks. -- Marco

5 10