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

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