On 05/01/18 21:34, Anton Aylward wrote:
The next simple step is to run CLI SSH with debug/verbose turned on:
-v Verbose mode. Causes ssh to print debugging messages about its progress. This is helpful in debugging connection, authentication, and configuration problems. Multiple -v options increase the verbosity. The maximum is 3.
If that does not enlighten you as to what is going on and let you make progress, then report it here and the Group Mind will advise :-)
That could be useful. Or indeed, that could have been useful, just the other week when I was at the other location. I was trying to set up ssh in the other direction to my main machine that I'd left switched on at home, but for some reason couldn't get it to work, despite all configs being effectively the same, and both ends running the same openSUSE version. The ssh-copy-id command would just hang and time out with some error I forget what. With previous occasional home power cuts in mind, I suspected I might arrive back and find the PC turned off, but no, it was on. I couldn't see anything obvious in the logs either. So I'm suspecting the router/ISP at my home end might be the culprit, but haven't looked into it enough yet. I assume some kind of 'reverse ssh' is a thing that exists, i.e. if I can ssh into the remote machine, I could attempt to configure and start a connection in the other direction from within that ssh session? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org