- atlas-sw-probes - mailman.ripe.net

Updated RIPE Atlas Software Probe Docker Images
by César de Tassis Filho 24 Jul '24

24 Jul '24

Dear RIPE Atlas Software Probe community, I am happy to share a significant update to the ripe-atlas-alpine project, which provides Docker images of the RIPE Atlas Software Probe using Alpine Linux. The Docker images have been updated to support the new version of the software probe, version 5090. This update includes a simplified build process and results in even smaller images than before. These Docker images are now available for a broader range of architectures, including: - linux/386 - linux/amd64 - linux/arm/v6 - linux/arm/v7 - linux/arm64/v8 - linux/ppc64le - linux/riscv64 - linux/s390x Please note that the transition from version 5080 to 5090 involves changes to the volumes that need to be mounted in Docker. I have updated the README documentation on both GitHub and Docker Hub to reflect these changes. This project remains experimental; feel free to report any bugs. For more details and to get started with the updated Docker images, please visit: - GitHub: https://github.com/CTassisF/ripe-atlas-alpine - Docker Hub: https://hub.docker.com/r/ctassisf/ripe-atlas-alpine Best regards, César

2 2

software probe application ssh pubkey
by Marco Moock 16 Apr '24

16 Apr '24

Hello! The application form for software probes includes a field for a public SSH key. Which purpose does it have? Is that the Pubkey of the future software probe or anything else? -- kind regards Marco Send unsolicited bulk mail to 1713255789muell(a)cartoonies.org

2 2

Compiling instructions for building from source
by Georg 28 Sep '23

28 Sep '23

Hi, I'd like to build the sofware probe from source for Archlinux, and would like to provide the resulting recipe (a so-called PKGBUILD) to the Arch User Repository as well. Reading through the build scripts for debian and centos left a few open questions, is there any direction on how to build the sw probe without these scripts? I'd like to avoid using the hardcoded libevent 2.1.11 or even a bundled busybox, is this possible and foreseen? A pointer to build instructions would be much appreciated. Thank you in advance Georg ps: after subscribing to this mailinglist I received a welcome message with a bunch of outdated links, you might want to consider updating them.

3 5

Big data opportunity?
by Andrew Prendergast 03 Jul '23

03 Jul '23

Hello Gents (and Ladies!), Can someone please point me to some resources on these probes? I would like to get a better understanding of the use cases we're trying to solve for, how they work & what they do, what data is coming out, where is the data stored, have we centralised and aggregated it, is there a data map, API docs etc. I would like to review the tech from a big data & analytics perspective and see if there is an opportunity to do data warehousing/vaulting/laking modernisation, maybe with some visualisations, dashboards & ML. I've got a spare Oracle M3 and a couple Dell R720s with 512GB / 384GB RAM (respectively) w/dual 10GB NICs + FC-AL cards, as well as a handful of Dell MD-1220 FC-AL arrays full of SSD disks that are currently disused sitting in Australia - could we make some use of that? Best Regards, ap --- Andrew Prendergast *Australian Computer Scientist + Information Security Specialist* M +61 409 941 901 <+61409941901> | ap(a)andrewprendergast.com blog.andrewprendergast.com | linkedin.com/in/aprendergast <https://www.linkedin.com/in/aprendergast/> ACS <https://www.acs.org.au/> | ACM <https://www.acm.org/> | INFORMS <https://www.informs.org/> | SIGGRAPH (Pioneer) <https://www.informs.org/> | auDA <https://www.auda.org.au/> | IEEE <https://www.itsoc.org/> | Internet Society <https://www.internetsociety.org/> Member MSc(CompSci), RMIT University | Cert. Advanced Cyber Security, Stanford University Top secret banking clearance, last updated 2023 (AU, US, UK, NZ). .\p

1 0

Acnhor Id 6037
by Hamed Khoramyar 02 Jul '23

02 Jul '23

HI Guys; We used to be a RIPE members for many years and we ran Anchor Id 6037 for several years. The anchor is now shutdown for more than 3 years, and I want to see if we can re-install it in a VM on one of the servers we operate. Is this possible? I like to keep the history and old anchor ID if possible. Thanks; -- Hamed Khoramyar Aivivid.com / IT Infrastructure and Cybersecurity services. Managing Director Office: +46-8-12144227 / Mobile / Signal: +46-763092020 Twitter: @khoramyar / @aivivid SnailMail: Box 1456, 11674 Stockholm, Sweden Member of The European Cyber Security Organisation (ECSO) Highest creditworthiness ranking (UC)

1 0

Instructions for updating software probe version
by mivens 11 Jan '23

11 Jan '23

Hello, I'm running a software probe on a Raspberry Pi running Raspian bullseye and from looking at /usr/local/atlas/state/FIRMWARE_APPS_VERSION I appear to be running version 5020. I note from https://atlas.ripe.net/docs/howtos/software-probes.html that as a host, I am expected to "Keep the version of your software up-to-date by upgrading to newer versions as they become available" but I have not found any explicit instuctions on how to do this. I would assume that it would be as simple as updating the local Github repo, and rebuilding the deb file from the main branch then doing a dpkg -i for the new Debian package to install the updated version. Unfortunately, it is not clear to me from looking at the repo what version I am expected to upgrade to. The CHANGES.rst file in the Github repo at https://github.com/RIPE-NCC/ripe-atlas-software-probe/blob/master/CHANGES.r… only mentions up to release 5040 but there are tags currently up to 5083 in the software-probe repo at https://github.com/RIPE-NCC/ripe-atlas-software-probe/tags which do not appear to be in any particular order. There are no releases listed at at https://github.com/RIPE-NCC/ripe-atlas-software-probe/releases The main probe release page at https://atlas.ripe.net/docs/releases/firmware.html mentions up to version 5080. Questions: Am I correct that I am should keep the software up to date? Are there instuctions on how to do this that I have missed? If not could the documentation could be updated with this and shared with the mailing list in the meantime? Many thanks

2 2

Software probe fails to register
by Matthieu Ducros 29 Sep '22

29 Sep '22

Hello I am trying to run software probe in a Docker container. But each initialisation fails with a very basic error "REGINIT exit with error” (see flow below). The public key is recorded already in RIPE web portal but the error remains at each startup. I tried both Bridge and shared network with the same issue. Is there a way to know more about the error ? Best Matthieu 022-09-29T15:42:57.379001202Z stdout 255 REGINIT exit with error 2022-09-29T15:42:57.177688598Z stdout ssh -p 443 atlas(a)193.0.19.246 <mailto:atlas@193.0.19.246> INIT 2022-09-29T15:42:57.176253785Z stdout REGHOSTS reg03.atlas.ripe.net <http://reg03.atlas.ripe.net/> 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net <http://reg04.atlas.ripe.net/> 193.0.19.247 2001:67c:2e8:11::c100:13f7 2022-09-29T15:42:57.173031723Z stdout REASON_FOR_REGISTRATION NEW NO previous state files 2022-09-29T15:42:57.172130959Z stdout ATLAS registration starting 2022-09-29T15:42:57.170780373Z stdout start reg 2022-09-29T15:42:57.170423886Z stdout Ping failed 2022-09-29T15:42:57.170019270Z stdout [warn] event_del_: event has no event_base set. 2022-09-29T15:42:57.116492305Z stdout /var/atlas-probe/status/reginit.vol does not exist try new reg 2022-09-29T15:42:57.116063805Z stdout RESULT 9006 done 1664466177 0242ac110002 no reginit.vol start registration 2022-09-29T15:39:56.916516214Z stdout condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists 2022-09-29T15:39:56.913936103Z stdout condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists 2022-09-29T15:39:56.907430444Z stdout 255 REGINIT exit with error 2022-09-29T15:39:56.899193700Z stdout ssh -p 443 atlas@2001:67c:2e8:11::c100:13f7 <mailto:atlas@2001:67c:2e8:11::c100:13f7> INIT 2022-09-29T15:39:56.897727021Z stdout REGHOSTS reg03.atlas.ripe.net <http://reg03.atlas.ripe.net/> 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net <http://reg04.atlas.ripe.net/> 193.0.19.247 2001:67c:2e8:11::c100:13f7 2022-09-29T15:39:56.894196731Z stdout REASON_FOR_REGISTRATION NEW NO previous state files 2022-09-29T15:39:56.893356284Z stdout ATLAS registration starting 2022-09-29T15:39:56.892452551Z stdout start reg 2022-09-29T15:39:56.892065716Z stdout Ping failed

1 0

Raspberry PI Images with Packer and questions
by Rodolfo García Peñas (kix) 21 Sep '22

21 Sep '22

Hello, I did a method to make Raspberry PI images for Atlas SW probes using Packer. https://github.com/thekix/ripe-atlas-sw-probe-packer After create this method, I have two comments: - The Raspberry PI image uses Debian. When the Debian package is installed, it launches the Atlas service. The atlas service creates the public and private keys. For this reason I can create the Debian package in the image creation with Packer, but I cannot install it. I am using an script in the first boot to install the package. - As I pointed in the previous comment, the keys are created when the package is installed. This is a good idea if the package is created for first time or if the user is updating the package. But if the user is moving the installation to a new device, when the package is installed, a new key-pair is created. Therefore, probably the user wants to replace the new keys with the previous and these keys will left unused (but registered). For these reasons, probably split the package installation and the service startup could be an idea. Then, the user can install the package, if the user has previous keys copy them to the keys folder and then launch the service. These steps (https://github.com/RIPE-NCC/ripe-atlas-software-probe/blob/master/INSTALL.r…) will change from: - Install this .deb file: sudo dpkg -i atlasswprobe-??????.deb - The public key is stored in /var/atlas-probe/etc/probe_key.pub - Then register your probe at https://atlas.ripe.net/apply/swprobe/ To - Install this .deb file: sudo dpkg -i atlasswprobe-??????.deb - If you have previous keys, from other SW probe, copy them to /var/atlas-probe/etc/ - Launch the service: sudo sytemctl start atlas - If you are using a new atlas probe, then: - The public key is stored in /var/atlas-probe/etc/probe_key.pub - Then register your probe at https://atlas.ripe.net/apply/swprobe/ What do you think? Best regards,kix -- Rodolfo García Peñas (kix) "I asked him once how to change the key bindings and Dave said 'You use the Change Configuration command. On Unix it is abbreviated as cc.' Dave Conroy and Lawrence Stewart.

4 5

Untagged releases in software probe repository
by Michel Stam 12 Jul '22

12 Jul '22

Hi Josef, I’m responding to you in a separate mail, because I had not received your mail via the mailing list. Sorry for messing up the thread. Anyway, we will be pushing the software probe repository, with tags, soon. The reason this was not done is that we were reorganising the internal GIT repository to better support automated builds, as well as to do some restructuring to facilitate development. This of course, does not affect the history. I would love to touch base with you regarding the OpenWRT package you’re maintaining. Thanks for reaching out! Best regards Michel

1 0

New releases are not tagged?
by Josef Schlehofer 10 Jul '22

10 Jul '22

Hello guys, I noticed that there should be new releases for Atlas SW Probe firmware according to the Technical Updates [1]. Still, it appears that they are not included in the master branch and are not tagged in the ripe-atlas-software-probe repository on GitHub [2]. Devel branch contains version up to 5060. It appears that someone else is also looking for them [3]. Would it be possible to tag new releases so I can update them in OpenWrt? [1] https://atlas.ripe.net/resources/announcements/ [2] https://github.com/RIPE-NCC/ripe-atlas-software-probe [3] https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/70 Looking forward to hearing from you, Josef Schlehofer

1 0