Hi Jiri,

On 17 Jan 2020, at 14:51, <ripe@brite.cz> <ripe@brite.cz> wrote:

Hi team, I have SW probe 1000069 running on router Turris Omnia. I had to commit factory reset and reinstall all software. All went good, I have the SW Probe running, got new SSH KEY [command "/etc/init.d/atlas get_key"] and pasted the new key to web > Update SSH Key. First it accepted, but the probe never managed to connect. I restarted the probe process and even whole router, also tried to get the key from the probe again and when pasting to Update SSH Key field it says "A probe with this key already exists. Please enter a unique key". So the new key is sure recorded correctly.

For some reason the new key was not copied to the probe. I have now done this manually so it should be able to connect now

Probe log: root@turris:~# /etc/init.d/atlas log 01/17/20 12:36:02 ctrl-init 01/17/20 13:39:02 net-try 01/17/20 13:39:05 net-ok 01/17/20 12:39:05 ctrl-init 01/17/20 13:42:06 net-try 01/17/20 13:42:09 net-ok 01/17/20 12:42:09 ctrl-init 01/17/20 13:45:09 net-try 01/17/20 13:45:12 net-ok 01/17/20 12:45:12 ctrl-init

From https://www.ripe.net/ripe/mail/archives/atlas-sw-probes/20191023/000002.html I read "We'll add a means to replace this key for an existing probe, in case you need to reinstall and lose the original key material." Does it mean it is not implemented yet?

It should be implemented… I will check on Monday why it failed to copy the new key to the probe. Cheers and have a good weekend :) Johan

Thank you

Jiri