- ripe-atlas - mailman.ripe.net

Atlas Account Disabled
by cassianoaquino＠me.com 22 Apr '25

22 Apr '25

Hi, I was trying to login to my atlas ripe account and forgot I had multiple authenticators configured and kept trying with the wrong one which gave me an error about the account being disabled to contact "your administrator". Now when I try to login it says "Invalid email address or password". Is there someone who can help me or point me on how to contact "your administrator"? The atlas login email is the same I use here on the mailing list. Thanks in advance!

1 0

how to delete a never used software probe
by Hans Mayer 17 Apr '25

17 Apr '25

Dear All, by a mistake I submitted the wrong SSH key during the installation of a software probe. Therefore I have now in my list of probes a second probe ID which is hidden and was never connected. Querying the Internet tells me Click on your probe and Click the "Write off your probe" function on the probe's detailed information page But when I do so I see an almost empty screen with the probe ID and "This probe was Never Connected" and nothing else. Any help is welcome. Kind regards Hans --

2 2

Decreasing number of probes
by Felix Hoffmann 09 Apr '25

09 Apr '25

Hey, I am currently running multiple scheduled measurements (ids: 85023653, 85023729, 85023782, 85023852). In the wizard, I selected the probes by area with the following settings: WW, 1000 probes. At the beginning of the measurements, mostly all probes reported, but meanwhile the number of probes reporting has decreased constantly. Is there an option to rotate the probes regularly to ensure a certain amount of active probes? Best regards, Felix Hoffmann

5 5

Atlas software probe on FreeBSD
by Marco Moock 09 Apr '25

09 Apr '25

Hello! Are there any people who have the RIPE Atlas software probe daemon running on FreeBSD? I have a virtual machine that could host a probe, although I haven't found any info if the daemon runs there. -- kind regards Marco Send unsolicited bulk mail to 1744132937muell(a)stinkedores.dorfdsl.de

2 1

Monthly probe reports for March 2025 missing?
by ripe＠nurfuerspam.de 07 Apr '25

07 Apr '25

Hi, I don't recall having seen the monthly probe report for March 2025, and also cannot find anything when explicitly looking for them. Did anyone else get the probe report for March 2025? In the past, they usually came in the very early hours of the first day of the month. Thanks! Kind regards, R.

2 2

RIPE Atlas Anchor Certificate Change
by Robert Kisteleki 07 Apr '25

07 Apr '25

Dear colleagues, We will be carrying out planned maintenance on RIPE Atlas anchors to replace the existing Lets Encrypt certificates with self-signed ones. There is no action needed by anchor hosts. The only visible change for users - should they want to visit an anchor URL using their browser - will be the standard notification asking them whether they trust the certificate before proceeding. This change is not expected to have a significant impact on functionality as the HTTPS service on RIPE Atlas anchors is not intended to be accessed by regular users in browsers but from measurements and scripts. Kind regards, Robert Kisteleki

1 0

Software Probe version 5110 released
by Trix Taiclet 02 Apr '25

02 Apr '25

Dear colleagues, We have released a new version of the RIPE Atlas Software Probe, version 5110. This 5110 release contains the following changes: * Added support for Raspberry Pi OS 12 (added Debian 12 arm64 package) * Rewrote GitHub README and BUILD instructions * Display Probe registration instructions during installation for RHEL and Debian * Generate Probe keys after installation without requiring service startup * Using the signing key introduced in 5100 to sign RHEL packages. The current RHEL key is deprecated as of this release. * Fixed compilation error by adding a missing include to telnetd.c (authored by César de Tassis Filho <ctassisf(a)gmail.com>) * Hardened the security of the RIPE Atlas service unit (reported by Marek Küthe <m.k(a)mk16.de>) * Added missing requirement for procps-ng on RHEL9 to RHEL probe package specfile (authored by Robert Scheck <robert-scheck(a)users.noreply.github.com>) * Document runtime options for custom TCP ports (authored by AtlasMUC <AtlasMUC(a)mail.de>) * Fixed typo in GitHub org url for RHEL ripe-atlas-anchor specfile (authored by Pouria Mousavizadeh Tehrani <info(a)spmzt.net>) * Fixed typo in GitHub org url for RHEL ripe-atlas-probe specfile (authored by eeple <m.renusson(a)gmail.com>) This release does not contain any functional changes to the measurement code. You can find more information and instructions on the GitHub repository: https://github.com/RIPE-NCC/ripe-atlas-software-probe/ You might have seen this release before our announcement; we faced an issue with the arm64 repo package, which caused us to delay that specific package and our announcement. Please let us know if you find any issues with this release. Regards, Trix Taiclet & Marios Mavropoulos RIPE NCC

1 0

How to set a probe non-public?
by Robby van de Meulenhof 01 Apr '25

01 Apr '25

Hello, At the moment i have 3 probes. 1 of the 3 probes i would like set non-public. With the new detail page i can't change the Shared Publicy (no checkbox like the old design) I switch to /Legacy Probe Detail/ i can *uncheck Shared Publicy* when i save it a get an error "You cannot make a public probe non-public." I can'tt find how i set a probe to non-public. How i do that? Regards, Robby

2 3

API-Key grants: There were problems with your request
by Bjoern Franke 01 Apr '25

01 Apr '25

Hi, I created a new API key and tried to set some measurements permissions. Yesterday evening and also now I'm only getting "There were problems with your request" and no grants are set. Regards Bjoern

1 0

Missing data in connection and uptime history for probe
by Anton Bobov 21 Mar '25

21 Mar '25

Hello! I am experiencing an issue with incorrect uptime and connection history for my probe (ID: 1006959 https://atlas.ripe.net/probes/1006959/network). I am currently running a software probe on Rocky Linux 8.10, with the probe version 5100. There was a power outage between 2025-03-14 04:25 and 2025-03-14 05:25 (UTC), which seems to have affected the data. I downloaded the connection history for the specified period, and it shows the following entries: seq timestamp (UTC) event stored_timestamp (UTC) ---------------------------------------------------------------------- 1 2025-02-08 23:13:51 disconnect 2025-02-08 23:13:51 2 2025-02-08 23:17:18 connect 2025-02-08 23:17:18 3 2025-03-14 04:25:35 disconnect 2025-03-14 04:25:36 4 2025-03-14 05:25:06 connect 2025-03-14 05:25:06 5 2025-03-14 06:49:19 disconnect 2025-03-14 06:49:19 6 2025-03-14 06:52:46 connect 2025-03-14 06:52:47 7 2025-03-15 22:36:49 disconnect 2025-03-15 22:36:50 8 2025-03-15 22:39:17 connect 2025-03-15 22:39:17 However, entries [2] to [7] are missing from the connection history, and only [1] (last disconnect) and [8] (last connect) are displayed. Additionally, this period is also missing from the uptime history. Could this be a bug, or is there another explanation for this issue? -- Cheers, Anton

2 4