- 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

SW probe package for Centos 7 unavailable?
by ripe＠brite.cz 07 Jul '22

07 Jul '22

Hi team, I'm installing SW probe on Centos 7, it seems the package is not available. I'm following https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/CentOS… linked by https://atlas.ripe.net/docs/software-probe/ It works until step 4 [yum install atlasswprobe], where I'm getting "No package atlasswprobe available". Any idea please? Cheers Jiri

1 0

RIPE Atlas Software Probe using Alpine Linux
by César de Tassis Filho 14 Sep '21

14 Sep '21

Hi, I've created Docker images of RIPE Atlas Software Probe using Alpine Linux. The main goal was to achieve the smallest image sizes possible and run them on MikroTik routers, now that RouterOS supports running containers[1]. The image size difference is quite impressive. While an exported tarball of a debian:10-slim image with atlasswprobe-*.deb installed reaches ~95MiB, my version based on Alpine is only ~15MiB. I had to make small changes to the code, like checkout devel branch on ripe-atlas-probe-busybox because it has fixes for musl and apply a patch that fixes syscalls for arm32v7. But other than that it is built using the same code provided for Debian. Images were compiled for amd64, arm64v8 and arm32v7 and they seem to work well on all 3 architectures. I have a probe running[2] on my MikroTik RouterBOARD using this code. It is not quite stable yet due to all the testing I have done, but it is there as a proof of concept :) *This is still a work in progress.* Maybe there's something not quite right. Please let me know if you find something. Code is available on GitHub[3]. Images on Docker Hub[4]. Best regards, César [1] https://forum.mikrotik.com/viewtopic.php?f=2&t=178437 [2] https://atlas.ripe.net/probes/1002873/ [3] https://github.com/CTassisF/ripe-atlas-alpine [4] https://hub.docker.com/r/ctassisf/ripe-atlas-alpine

2 1

Probe Registration and Connection Problems
by İlteriş Yağıztegin Eroğlu 07 Apr '21

07 Apr '21

Hello, I have registered the software probe 1002204 on my infra and I believe rebooting multiple times in short time span made the connections ratelimited. Are there any other issues on RIPE's end? I can see that telnetd is running. ``` root@as208563-probevm:~# ps aux | grep telnetd atlas 2030 0.0 0.0 8108 388 ? Ss 11:48 0:00 /usr/local/atlas/bb-13.3/usr/sbin/telnetd -b 127.0.0.1 -p 2023 -P /var/atlas-probe/run/telnetd-port2023-pid.vol root 2801 0.0 0.0 6432 660 pts/0 S+ 12:27 0:00 grep --color=auto telnetd root@as208563-probevm:~# ``` Kind Regards, Ilteris

2 1

Software probe core dump?
by Ulrich Wisser 18 Nov '20

18 Nov '20

Hi, I installed my software probe on docker today It seems the software tries to change some permissions and crashes. IS this normal? /Ulrich chmod: changing permissions of '/var/atlas-probe/data': Operation not permitted perd: in my_exit (exit was called!) Aborted (core dumped) eperd: in my_exit (exit was called!) Aborted (core dumped)

2 2

Re: [atlas-sw-probes] Probe connection drops around every hour.
by Tiago Freire 17 Sep '20

17 Sep '20

The probe number: 1000907 Thanks in advance.

2 2

Re: [atlas-sw-probes] Probe connection drops around every hour. (Philip Homburg)
by Tiago Freire 01 Sep '20

01 Sep '20

The probe number: 1000907 Thanks in advance.

2 1

Probe connection drops around every hour.
by Tiago Freire 01 Sep '20

01 Sep '20

The probe number: 1000907 Thanks in advance.

1 0

Probe connection drops around every hour.
by Tiago Freire 31 Aug '20

31 Aug '20

Hello. I successfully deployed two new software RIPE probes, but one of them is behaviouring strangely, dropping its connection on multiples of 1 hour period: [image: imagem.png] [image: imagem.png] This probe is behind a double NAT and through a WISP, with its first hop gateway on a DMZ. [image: imagem.png] I'm using the 5020 source code on this software probe. Can anyone kindly help on this? Thanks. Best regards.

2 1

Registration issues starting Jul 27
by İlteriş Yağıztegin Eroğlu 27 Jul '20

27 Jul '20

Atlas mailed me a while ago for probe downtime (ID 1000023), though my network is still working. I also have seen a high amount of (re-)connections from today (July 27th) which is also weird. You can see them on https://atlas.ripe.net/probes/1000023/#!tab-network I also got a journalctl snippet available on https://paste.debian.net/plainh/cacd78f8 Regards, Ilteris

2 3

How to force the SW Probe to use particular IP Interface / IP Address?
by ripe＠brite.cz 19 Jun '20

19 Jun '20

Hi team, is there a way how to force the SW Probe to use particular IP Interface / IP Address? 1. Turris Omnia Router: 1a - there is public IPv4 on WAN interface, but the probe choose LAN interface that is behind NAT, what is not necessary and would be better to choose the WAN. 1b - I have multiple IPv6 interfaces, the probe keeps choosing the one I use for testing and therefore is not as stable as the others. I would like the probe to use WAN6 interface instead. 2. CentOS virtual machine - there is public IPv4 and local IPv4 RFC1918, again, the probe choose the local instead of the public IP. It's a pity, the probe better use the public one. Take Care Jiri

3 6

Turris SW probe - long time to connect
by Jan Pavlinec 08 Jun '20

08 Jun '20

Hello, Since this week based on report [1], [2] from Martin we were able to observe his issue, which he reported and by using Atlas SW Probe 5010 and older, we noticed that in CLI probe is running and that it is doing something, but on the RIPE website, it shows that probe is disconnected. Can you please check probes IDs (1000585, 1000243) and what it took so long to show that it is connected? Both of those probes were shown as connected at the same time - 20:22) on Tuesday? We noticed that in some cases if you were using the latest version 5020 and register a new probe, it is working within a few minutes. However, we pushed to all our Turris OS version updated Atlas SW Probe to version 5020 and some of our users noticed similar maybe the same behavior. A probe was running on the router, but it was disconnected for almost an hour (probe ID 1000036) The router is working in all cases, ping, dig connection is OK. I'm wondering if this issue isn't on server side. In reg_init_reply.txt were following data: WAIT TIMEOUT 115 Do you know how to debug it more? [1] https://forum.turris.cz/t/turris-os-5-0-0-is-released-in-hbt/12733/149 [2] https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/38 Looking forward to hearing from you, Jan

3 3

Fwd: Problem with registration
by Nikolaos Antonatos 07 Jun '20

07 Jun '20

Hi, Recently I have to reinstall the OS on the Atlas SOFT probe and I decide to go to ubuntu. I ve follow all the instructions and start the atlas service. the problem is that its not registered. I have change the SSH pubkey in the portal Why its not working? LOGS: Jun 7 21:31:09 atlas ATLAS[24081]: RESULT 9006 done 1591558269 36ef89dfc192 no reginit.vol start registeration Jun 7 21:31:09 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:31:12 atlas ATLAS[24081]: And we are done Jun 7 21:31:12 atlas ATLAS[24081]: Ping works Jun 7 21:31:12 atlas ATLAS[24081]: start reg Jun 7 21:31:12 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:31:12 atlas ATLAS[24081]: REASON_FOR_REGISTRATION NEW NO previous state files Jun 7 21:31:12 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:31:12 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)193.0.19.247 INIT Jun 7 21:31:14 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591558403 Jun 7 21:31:14 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists Jun 7 21:34:14 atlas ATLAS[24081]: Moving reboot-count.txt Jun 7 21:34:14 atlas ATLAS[24081]: RESULT 9006 done 1591558454 36ef89dfc192 no reginit.vol start registeration Jun 7 21:34:14 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:34:17 atlas ATLAS[24081]: And we are done Jun 7 21:34:17 atlas ATLAS[24081]: Ping works Jun 7 21:34:17 atlas ATLAS[24081]: start reg Jun 7 21:34:17 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:34:17 atlas ATLAS[24081]: unknown keyword 'REG_WAIT_UNTIL' in CON_INIT_CONF (1) Jun 7 21:34:17 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:34:17 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)193.0.19.247 INIT Jun 7 21:34:19 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591558582 Jun 7 21:34:19 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists Jun 7 21:34:19 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists Jun 7 21:37:19 atlas ATLAS[24081]: RESULT 9006 done 1591558639 36ef89dfc192 no reginit.vol start registeration Jun 7 21:37:19 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:37:22 atlas ATLAS[24081]: And we are done Jun 7 21:37:22 atlas ATLAS[24081]: Ping works Jun 7 21:37:22 atlas ATLAS[24081]: start reg Jun 7 21:37:22 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:37:22 atlas ATLAS[24081]: unknown keyword 'REG_WAIT_UNTIL' in CON_INIT_CONF (1) Jun 7 21:37:22 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:37:22 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)193.0.19.247 INIT Jun 7 21:37:24 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591558766 Jun 7 21:37:24 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists Jun 7 21:37:24 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists Jun 7 21:40:24 atlas ATLAS[24081]: RESULT 9006 done 1591558824 36ef89dfc192 no reginit.vol start registeration Jun 7 21:40:24 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:40:27 atlas ATLAS[24081]: And we are done Jun 7 21:40:27 atlas ATLAS[24081]: Ping works Jun 7 21:40:27 atlas ATLAS[24081]: start reg Jun 7 21:40:27 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:40:27 atlas ATLAS[24081]: unknown keyword 'REG_WAIT_UNTIL' in CON_INIT_CONF (1) Jun 7 21:40:27 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:40:27 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)reg03.atlas.ripe.net INIT Jun 7 21:40:29 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591558944 Jun 7 21:40:29 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists Jun 7 21:40:29 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists Jun 7 21:43:29 atlas ATLAS[24081]: RESULT 9006 done 1591559009 36ef89dfc192 no reginit.vol start registeration Jun 7 21:43:29 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:43:32 atlas ATLAS[24081]: And we are done Jun 7 21:43:32 atlas ATLAS[24081]: Ping works Jun 7 21:43:32 atlas ATLAS[24081]: start reg Jun 7 21:43:32 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:43:32 atlas ATLAS[24081]: unknown keyword 'REG_WAIT_UNTIL' in CON_INIT_CONF (1) Jun 7 21:43:32 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:43:32 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)reg03.atlas.ripe.net INIT Jun 7 21:43:33 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591559141 Jun 7 21:43:33 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists Jun 7 21:43:33 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists Jun 7 21:46:33 atlas ATLAS[24081]: RESULT 9006 done 1591559193 36ef89dfc192 no reginit.vol start registeration Jun 7 21:46:33 atlas ATLAS[24081]: /var/atlas-probe/status/reginit.vol does not exist try new reg Jun 7 21:46:36 atlas ATLAS[24081]: And we are done Jun 7 21:46:36 atlas ATLAS[24081]: Ping works Jun 7 21:46:36 atlas ATLAS[24081]: start reg Jun 7 21:46:36 atlas ATLAS[24081]: ATLAS registeration starting Jun 7 21:46:36 atlas ATLAS[24081]: unknown keyword 'REG_WAIT_UNTIL' in CON_INIT_CONF (1) Jun 7 21:46:37 atlas ATLAS[24081]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 Jun 7 21:46:37 atlas ATLAS[24081]: ssh -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)193.0.19.246 INIT Jun 7 21:46:38 atlas ATLAS[24081]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1591559315 Jun 7 21:46:38 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists Jun 7 21:46:38 atlas ATLAS[24081]: condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists ==> con_init_conf.txt <== REG_WAIT_UNTIL 1591559496 ==> currenttime.txt <== 1591559383 ==> p_to_c_report_header <== P_TO_C_REPORT ==> p_to_r_init.in.vol <== P_TO_R_INIT TOKEN_SPECS fluffy 1000 5020 debian-atlasswprobe-5020-1 REASON_FOR_REGISTRATION NEW ==> reg_init_reply.txt <== WAIT TIMEOUT 113 ==> ssh_err.txt <== -- Nikolaos Antonatos

1 0

Re: [atlas-sw-probes] How to force the SW Probe to use particular IP Interface / IP Address?
by Philip Homburg 25 May '20

25 May '20

On 2020/05/25 16:24 , jsuchan(a)centrum.cz wrote: > - how can I have my probe 1000069 not tagged IPv4 RFC1918? There is not much that can be done here. It is an automated process. Of course removing all interfaces with RFC 1918 addresses would do the trick. > - how can I make the probe use the default outgoing interface mentioned above? The probe just reports all of it's addresses. It is our backend system that needs to be improved. I can see that this is an issue. But I don't know how busy the people are who should implement this change. Philip

1 0

All IPv6-only software probes offline?
by Maurice Walker 12 May '20

12 May '20

Hey, It seems that all IPv6-only software probes are shown as offline since about 2020-05-12 12:48:30 UTC. I can't see anything wrong with my own probe (which is also affected). It has working Internet access and I rebooted it just to make sure. Could this be a server-side or routing issue? #1000018, #1000075, #1000076, #1000101, #1000169, ... Cheers Maurice

2 1

Software probe registered but not yet created
by Swapneel Patnekar 11 May '20

11 May '20

Hello! I've registered a software probe successfully on Ubuntu 16.04.4 LTS but it hasn't created it yet. Usually, this is done in 10-15 minutes. The machine is behind a pfSense firewall which as far as I can tell isn't blocking any requests. Can you share a troubleshooting checklist which I can try to see where the problem is? If I may make a suggestion to also update the troubleshooting page[1] for software probes Thank you. [1]: https://atlas.ripe.net/docs/troubleshoot-probe-issues/ -- Best, Swapneel https://brainattic.in/blog

1 0