You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be awesome if their was a command that I could use once done with the reverse tunnel to close/exit the remote process running the tunnel; so when I'm done with the tunnel I could exit/stop the tunnel from the server that its connected too, so that i could use the same port for multiple sessions if that makes sense. At the moment to disconnect/exit the connected remote process I'm having to restart the ssh server, which means i lose any other connected clients to the server, is their any way that you could implement some sort of exit command or make an argument so that once the first sh/bash session has exited that it closes the reverse tunnel and exits? Like a one-shot mode or something like that, Hoping the feature request makes sense
The text was updated successfully, but these errors were encountered:
It would be awesome if their was a command that I could use once done with the reverse tunnel to close/exit the remote process running the tunnel; so when I'm done with the tunnel I could exit/stop the tunnel from the server that its connected too, so that i could use the same port for multiple sessions if that makes sense. At the moment to disconnect/exit the connected remote process I'm having to restart the ssh server, which means i lose any other connected clients to the server, is their any way that you could implement some sort of exit command or make an argument so that once the first sh/bash session has exited that it closes the reverse tunnel and exits? Like a one-shot mode or something like that, Hoping the feature request makes sense
The text was updated successfully, but these errors were encountered: