-
Notifications
You must be signed in to change notification settings - Fork 185
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
QUESTION: How to avoid ssh tunnel timing out? #202
Comments
There are some cases:
Currently, we don't have timeout options for the case1. We can add it as a new feature in future releases. The case2 is configured on the server-side and depends on the ssh server. You can prevent case 3 by using We also have |
Thanks for the answer @pahaz. I think that along with the |
Probably, it’s better to set it by default in a future major release.
… On 30 Oct 2020, at 18:12, Luis Chaves Rodriguez ***@***.***> wrote:
Thanks for the answer @pahaz <https://github.com/pahaz>. I think that along with the set_keepalive option in paramiko and this I am able to sustain a longer SSH session!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKUK2JVOMIEXBWYRHJPE7TSNLJVNANCNFSM4TEDG52A>.
|
Hello, I would like to know a couple of things:
I've read a few options in stack overflow and the pull request #156 but I am not confident SSH_TIMEOUT is what I am looking for, could you clarify my doubts?
The text was updated successfully, but these errors were encountered: