Portsdown and Jetson SSH problem

[G4WIM]

I've got something odd going on (again).

I've just built a new Jetson image and it works fine by ssh into it to set the various parameters etc so I know I have the right username and password etc. PIcam works, IP source works.

But when I try to control it from Portsdown with the same parameters nothing happens - can't even shut it down.

Using wireshark I see SSH session being set up but not sure if it's successful, I also notice that F5OEO made a change to nanoencode.sh a couple of months back.

Portsdown works ok with an earlier Jetson image so suspect something has changed.

Any ideas on how to debug / fix ?

73 Tim

[g0mjw]

You may have changed the trust certificate. Try SSH from the PI to the Jetson. Then accept and save the new identifier. It will then work hopefully.

Mike

[G4WIM]

Hi Mike,

good idea - hadn't thought of that !

Will report back later.

73 Tim

[G4WIM]

Hi Mike,

that did the trick - just had to remove the old key from trusted hosts on the rpi and all is good again !

This may help others when they're trying out different combinations and run into the same problem of not having ssh working properly.

73 Tim