Dear colleagues, On 10/01/2026 19:48, Marek Zarychta via ripe-atlas wrote:
W dniu 10.01.2026 o 17:11, Sulev-Madis Silber via ripe-atlas pisze:
On January 10, 2026 5:56:26 PM GMT+02:00, Marco Moock <mm@dorfdsl.de> wrote:
What is the current state of the fork?
Does it now work?
Did RIPE already decided if they want to merge the changes for FreeBSD?
The PR [0] contains a lot of changes, not only FreeBSD support. We're very willing to merge general fixes, but they're tangled up with FreeBSD/Apple-specific changes. To be clear, we are open to merging a FreeBSD PR, but we simply do not have the resources to maintain it in the long-term, given the current structure of the probe code.
The PR(s) should apply cleanly and work, but there doesn't seem to be consensus about this currently. The PR in it's current state is not necessarily easy to review, given the commit history, and some code could use clean-up. (e.g. "FreeBSD specific commands could go here", but there is nothing FreeBSD specific, or the completely separate architecture, when there are already a few unused architectures, or some unexplained changes) Preferably, we'd first merge general fixes, before merging FreeBSD changes. I have to say that a lot of this is to blame on the current situation of the repo, which is not necessarily easy to work with, but we are trying to improve things. :)
last time i tried, battled, patched, ... with it, it didn't work, nor was i able to get it working
so no, it doesn't work
maybe some fbsd hacker can help?
Hi,
I’ve had a similar experience. I prepared a port to make building easier. It does build, but it’s not working correctly. If anyone wants to test and improve Jarred’s fork, here is the port [1] and some feedback [2] from people who tested it.
It would be nice, but probably difficult, to somehow convince the RIPE NCC staff to make the Atlas Software Probe code portable and less Linux-dependent. Our activity plan lays out 2026 [1], and one focus is "making the probe firmware code easier to maintain", which includes both software and hardware probes. As we've already reworked the software probe *process* recently, we're spending more time on the hardware probes, but we're open to PRs.
-- Regards, Trix Taiclet Embedded Systems Engineer @ RIPE Atlas RIPE NCC [0]: https://github.com/RIPE-NCC/ripe-atlas-software-probe/pull/135 [1]: https://www.ripe.net/media/documents/ripe-850.pdf