- ripe-atlas - mailman.ripe.net

Re: Change git to repository (Randy Bush)
by ripe＠nurfuerspam.de 14 Oct '24

14 Oct '24

> and how does one "using the UI to replace the key?" On your probe's management page (e.g., https://atlas.ripe.net/ probes/1000006/), at the bottom of the page under the "General" tab, there is the option to add a new key. On a 5080 software probe, unless paths were changed during the build, one should find the public ssh key under /var/atlas-probe/etc/probe_key.pub (at least that's where it is on my Debian 12 system).

2 1

Change git to repository
by Jimmy Huybrechts 14 Oct '24

14 Oct '24

Hi, Currently my software probe on Debian 12 is using the git repository as there was no official deb when mine was deployed. Now I wish to change it out for the official repo, how can this be done? Or should I register the repository one as a new probe? -- Jimmy

4 6

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

probes do not register
by Randy Bush 10 Sep '24

10 Sep '24

on a SOHO LAN that used gto have a good running v3 probe (25867 but it went where so many v3 probes go, dead for a few months now. yes i did usb recovery, to no avail. you gotta love v3 probes.) i unpack an unused v3 (25909) i had in my back pocket for a few years. plug it into the LAN. wait a few hours. it does not register. power LED on, LED to right of it blinks about every two seconds. web page for it, https://atlas.ripe.net/probes/25909/ shows it has been down for 1 year 11 months while, in fact, it has never been up. oddly that web page shows the correct AS, comcast, 7922, but no IP addressing. tcpdump is my friend. pcap can be found at https://archive.psg.com/240907.atlas-25909.pcap it gets dhcp etc. then twice successfully pings to nl-ams-as3333-3.anchors.atlas.ripe.net (193.0.0.164) then it does successful DNS AAAA queries for woolsey.atlas.ripe.net and reg02.atlas.ripe.net. but it never reaches out to them that i can see. then it does a successful ARP for the default gateway, 192.168.0.1 then silence and much more silence unpack another unused antique from its envelope, 25918. dns queries for different controllers, but otherwise the same story. pcap avaliable as https://archive.psg.com/240907.atlas-25918.pcap. how to further debug? randy

3 5

RIPE Atlas Anchor Operating System Upgrade
by Paul de Weerd 02 Sep '24

02 Sep '24

Dear colleagues, RIPE Atlas anchors are scheduled for an Operating System (OS) upgrade soon since the current OS will reach its end-of-life on 30 June 2024 [1]. We are currently implementing and testing the necessary changes to support a smooth transition to the new OS without service interruption. Consequently, all live anchors will be upgraded by 31 August 2024. During this period, anchors will run on an outdated OS for a couple of months, but we do not anticipate any security issues here. For the few outward-facing services or lower-level software (such as the kernel) running on anchors, we will provide backports of necessary packages. If needed, we will shut down affected services or the anchor until the upgrade is complete. Due to this upgrade process, we have now paused applications for new anchors. New applications will resume from 15 July 2024 with anchors that will be provisioned with the new OS. If you have any questions please email gii-requests(a)ripe.net. Kind regards, Paul de Weerd RIPE NCC [1] https://www.redhat.com/en/topics/linux/centos-linux-eol

3 4

account e-mail change?
by Fallon Albrecht 29 Aug '24

29 Aug '24

Hi there, Thank you for your feedback. For security reasons, it is unfortunately not possible to change your RIPE NCC Access e-mail address. More information on this topic is available at: https://www.ripe.net/publications/documentation/disclosures-and-reports/rip… However, you can do the following: - Create a new RIPE NCC Access account with the new email address https://access.ripe.net/registration - You will need to enable two-factor authentication (2FA) to activate the account. - Transfer Atlas credits to the new SSO account If you need help or have any questions about this procedure, please contact ncc(a)ripe.net. We are always striving to improve RIPE NCC Access and our current work plans are available at : https://www.ripe.net/publications/documentation/quarterly-planning/business… Kind regards, Fallon Albrecht Product Owner RIPE NCC

1 0

Re: Globalping
by Ernst J. Oud 27 Aug '24

27 Aug '24

Stephane, That is precisely why I became interested, for a quick ping or trace they have a CLI where one can do a quick measurement or via the API. With Atlas Magellan in a docker container this is also possible, it streams the results to the console but Globalping might be a good add on tool in the toolkit. Thanks for the input. Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud > On 27 Aug 2024, at 14:03, Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote: > > On Tue, Aug 27, 2024 at 12:42:18PM +0200, > Ernst J. Oud <ernstoud(a)gmail.com> wrote > a message of 12 lines which said: > >> It might be “cursing in the church” as we say in NL, but does anyone >> here have experience with the Globalping monitoring tools? > > https://www.jsdelivr.com/globalping ? > > No real practical experience but it seems interesting. The API is > well documented and a shell script as simple as: > > curl -H "Content-Type: application/json" \ > --data-binary @- \ > https://api.globalping.io/v1/measurements \ > <<EOF > { > "limit": 10, > "locations": [], > "target": "ayla.bortzmeyer.org", > "type": "ping", > "measurementOptions": { > "packets": 3 > } > } > EOF > > is enough to launch a measurement. You can see the resulting JSON at > https://api.globalping.io/v1/measurements/bqXml2MiDAoawobv if you want > an idea.

2 1

account e-mail change?
by Sulev-Madis Silber 27 Aug '24

27 Aug '24

i noticed i can't change my account mail address. unsure why we have such limitation here. i have mail i used for 25 years, or literally more than half of my entire lifetime, and now i want to change it. reason being it's ispmail i had since dialup. and they sold it. now i still have access to it but service sucks, despite expensive. a very good reason to change it. yet ripe seems to have account mail is permanent policy for no reason at all. i expect this to change after more updates. there was huge ui update but this feature is not coming. why? most of things allow me to change mail. with only handful of services insisting it being for life. i don't know if next one is lifetime long but at least now it's my own domain. hoping to change it. or at least given reason why i can't

5 8

Globalping
by Ernst J. Oud 27 Aug '24

27 Aug '24

L.S. It might be “cursing in the church” as we say in NL, but does anyone here have experience with the Globalping monitoring tools? Not as comprehensive as Atlas and a lot less probes but at first glance it has some useful features. Your thoughts? Regards, Ernst J. Oud

3 2

Call for presentations for LACNIC's Internet Measurements Working Group (IMWG)
by Elisa 27 Aug '24

27 Aug '24

Hi all, Call for presentations is now open! Seeking presentations on Internet Measurements (including, but not limited to, Atlas). The Internet Measurements Working Group session will be held at the LACNIC42/LACNOG2024 meeting in Asunción, Paraguay, on October 11. Presentations can be remote or in-person. Submission deadline September 20. Instructions: https://listas.nog.lat/archives/list/imwg@listas.nog.lat/thread/VSNIWWLMXGI… Kind regards, -- 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

Update on RIPE Atlas Service Issues
by Robert Kisteleki 26 Aug '24

26 Aug '24

Dear colleagues, After the mails to this list over the weekend, we just wanted to confirm that we are aware of the issues some of you are having and we are working to resolve them. A service announcement has already been posted, as some of you have already pointed out. We would also like to note that probes will automatically try to re-connect to the RIPE Atlas infrastructure as long as they are operational. This is not something the host can control and so there is no action needed on your part. Currently, we are in the final stages of re-working the probe-controlling parts of the RIPE Atlas infrastructure, and while we’re careful to keep the machinery running, we expect to encounter some hiccups as we complete this work. During this period, there might be additional issues that arise which affect network performance or the connectivity of probes. We will try to keep this list updated, but note that you can always find the status of our services on status.ripe.net, and we encourage you to check if there are known issues. Regards, Robert Kisteleki RIPE NCC

1 0

Disconnected probes…
by Ernst J. Oud 26 Aug '24

26 Aug '24

All, Some of my disconnected probes have connected again, but probe 60200 has not. This is not a network issue since on that router a SW probe (1005072) now connects fine (it was disconnected earlier today) Would restarting probe 60200 help? It is in an inconvenient place but if restarting helps let me know. Regards, Ernst J. Oud

2 1

Probe v3 id #22785 - BADMD-APP
by Cassiano Aquino 26 Aug '24

26 Aug '24

Hi, I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working. I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again. Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e Is there anything else I can do? Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe? Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed! Cheers, Cassiano Aquino - EI5HPB

3 3

Fwd: Your RIPE Atlas Probe (ID: 60200) has reconnected
by Ernst J. Oud 25 Aug '24

25 Aug '24

> We're just letting you know that your probe (#60200 ) has re-established its link to our network and we are again receiving data from it. Good! After over 3 days. Connected to controller ctr-nue17. Not to ctr-dub anymore. Ernst

2 1

Probe v3, problems
by Phillip Remaker 24 Aug '24

24 Aug '24

I tried to replace by failing v2 probe with a v3 probe I had mailed to me from a closed site https://atlas.ripe.net/probes/16058/' The first led is on, second is off, and 3rd is slow-blink, which indicates a "network problem"? I tried a different power supply, replaced the network cable, tried other ports and even put in a new power supply, all with no change. The DHCP server does not see it. Any other suggestions?

1 1

Disconnected #27262
by Victor TALVAZ 24 Aug '24

24 Aug '24

Hi everyone, It seems that I've been totally disconnected for 2 hours, 8 minutes, is the controller ctrl-dub-hw01 alive ? Probe #27262. Thanks, Regards, *Victor TALVAZ*

3 2