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

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

How to remove unused SW-Probe
by ripe＠groetzner.net 08 May '20

08 May '20

Hello, how can I remove a unused VM-Probe? I don`t think „transfer ownership“ ist he right solution for an SW-Probe 😉 Sascha

4 3

New release v5020
by Philip Homburg 08 May '20

08 May '20

Hi, I just pushed version v5020 to github (https://github.com/RIPE-NCC/ripe-atlas-software-probe/tree/v5020) The main change is to the 'SOS' mechanism. Probes look up a special DNS name just before they try to connect. This can be used to diagnose probes that have trouble connecting. For hardware probes we rely on the probe's ethernet address to distinguish between probes. For software probes that doesn't work because we don't record ethernet addresses for software probes. We made a change to have software probes send the hash of the probe's public key instead. With this change the network tab of the probe page shows the 'SOS History'. >From this release we now also support CentOS 8 binary packages, though I noticed that we did not yet add that to the installation instructions. Finally, we changed the way we accept SSH public keys. We now accepts longer RSA keys (max. 4096 bits) as well as ECDSA and ED25519 Philip Homburg

2 2

Fwd: Thank you for applying for a RIPE Atlas software probe
by Georgi Vasilev 08 May '20

08 May '20

Hello, May I ask you to check, what is the problem with my probe. Here is the link https://atlas.ripe.net/probes/16362/ Thank you in advance Br, Georgi Vasilev ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Thu, Jan 30, 2020 at 12:25 PM Subject: Thank you for applying for a RIPE Atlas software probe To: Georgi Vasilev <georgi.petkov.vasilev(a)gmail.com> Dear Georgi Vasilev, Thank you for applying for a RIPE Atlas software probe! Your application ID is 91. If your application was successful, you will receive another email with the probe ID and additional instructions. We appreciate your support of the RIPE Atlas network. If you have any questions or concerns, please don't hesitate to contact atlas(a)ripe.net Kind regards, RIPE Atlas Team

2 1

Problem with UDM
by Thierry Montigneaux 20 Apr '20

20 Apr '20

Hi, I have just activated my first sw probe, on a dedicated CentOS7 VM, id 1000408. Out of habit, I did configure CentOS the way I usually configure my servers, notably by running OpenSSH on a non-default port and by activating only the ed25519 host key in sshd_config. I noticed 3 issues after having let the atlas-probe service run for a while, which included a couple of service restarts : 1. The SOS History table for the probe on the probe web page was not being populated with any data after the restarts. 2. The ./status/ssh_err.txt file showed the following message: « RSA host key for IP address '178.63.8.31' not in list of known hosts. » 3. I tried to set up a test one-off measurement using my sw probe by manually selecting its ID on the measurement setup screen, but it would not register the probe. I also noted after 12+ hours that no UDM was active for the probe from other users (from my experience with a hardware probe I have been operating for a while, it should be put at use by the network pretty quickly unless I am too impatient here ;-) ). My first action was to revert OpenSSH to default settings (use port 22, activate the RSA host key). This apparently contributed to solving problem 1 as the SOS History data started to appear on subsequent service restarts. Concerning the SSH error logged for the probe, the RSA Key for 'ctr-fsn01.atlas.ripe.net' was present in /var/atlas-probe/.ssh/known_hosts, but there was no entry in the file for a key for the corresponding IP address 178.63.8.31. I tried to add it to the probe known_hosts file but it disappeared after restarting the service. I guess the file is overwritten on service restart. I then added an entry for the RSA key for the IP address in the global /etc/ssh/ssh_known_hosts. The SSH error disappeared from the probe log file on the following service restart. So problem 2 solved for me, but that raises the question of whether there is a key missing for the probe known_hosts file for that IP address ? Now I am left with problem 3 and I have no clue as to why I can’t create a UDM which uses my sw probe ID. The built-in measurements seem to work fine if I read the probe web page info correctly. Any help welcome. Thierry

3 3

Missing DNS resolution system tags
by Maurice Walker 24 Feb '20

24 Feb '20

Hello, My software probe has been connected for about ten days now. It is in an IPv6-only network and was assigned IPv6 capable, works and stable system tags. But it was not assigned any DNS resolution tags yet, neither positive nor negative. I'm not aware of any DNS issues and its measurements seem okay. I searched for similar probes and it seems that all IPv6-only software probes are affected. Software probes with working IPv4 do have DNS tags, so do IPv6-only hardware probes. Cheers, Maurice

1 0