-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH Server doesn't close #87
Labels
Comments
how do you recommend avoiding or working around this? sorry I'm of no help |
evanlinjin
pushed a commit
that referenced
this issue
Mar 4, 2019
* combined link and instance into messaging * removed Makefile from messaging discovery * renamed some cmd files * updated dependencies and added 'dep' to Makefile * force travis to use xenial.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have encountered an issue of the SSH Server and SSH Client functionality of the manager web interface while creating the recent SSH guide on the wiki.
Issue: If you started the SSH Server once, other Skywire nodes are still connected to you even after closing the SSH Server using the manager GUI. The incoming connection will not be displayed so you have no visual confirmation if there is a connection established.
To test out the SSH connect function the two nodes need to be on different subset, the SSH server is on 10.0.0.0/24 subnet and the SSH Client is on 192.168.220.0/24 subnet. All displayed keys are test keys so you can't reproduce the issue using the displayed keys.
Start the SSH Server:
Then connect the SSH Client:
Results in this (working established from the SSH Client):
Displayed from the SSH Server side:
Check if the SSH connection can be utilized:
Now if you close the SSH Server the connection of the SSH Client stays open:
The process responsible for opening incoming connections on the SSH Server pi gets terminated correctly.
As you can see the displayed public key on the right terminal window is exactly the public key of the SSH Server pi that should not be connected anymore.
In difference to #83 the displayed connection actually fails and displays it visually after the SSH server was closed or after the remote pi was rebooted:
After a reboot you cannot establish a SSH connection to the SSH Server, tested it by obtaining the SSHS key from the file system without actually using the SSH Server start function within the web interface.
Best regards
The text was updated successfully, but these errors were encountered: