-
Notifications
You must be signed in to change notification settings - Fork 359
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
wstunnel stdio does not exit / stuck in a loop #93
Comments
Hello, Thanks for reporting ! 🤔 |
Any update on this issue? When using wstunnel with ssh, we want wstunnel to exit if the server closes the connection, but currently we get the infinite loop of error messages described above. Is what we need a command-line option that tells wstunnel to exit immediately in the case its initial connection, once made, is clsed? |
Will try to get a look at it this week, and coming back to you |
Hey, |
Thanks for doing this. I've tested the mac version, in conjunction with Here are before and after logs from an ssh connection made via wstunnel, when the remote wstunnel dies. Before:
After:
Will the new version need a command line option that enables the new behaviour, or do you feel the new behaviour is better in all cases? |
I think I will not add a flag, and make this behavior the default. So I will make it the default and see if some users complains |
Makes complete sense. |
Available in https://github.com/erebe/wstunnel/releases/tag/v6.0 |
I have a problem to get wstunnel -L stdio work with some software. It looks like wstunnel doesn't exit and tries to connect again and again. Simple example
This does work though:
(port 1080 is wstunnel)
There are also no issues with ssh and
ProxyCommand wstunnel -L stdio:...
The text was updated successfully, but these errors were encountered: