-
Notifications
You must be signed in to change notification settings - Fork 887
agent: Add support for keep-alive SSH messages #7581
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
Milestone
Comments
@kylecarbs @code-asher Any thoughts about this? |
I would love to see support for keep-alive, it seems like the
ideal solution for the idle issue.
We could also work around it on the extension side for now by
setting `ServerAliveInterval` right?
|
There are 2 use cases:
|
Ahhh my bad, I completely forgot we use our own SSH server. I
thought this would just be a matter of setting
`ClientAliveInterval` on the agent or something like that and
figured `ServerAliveInterval` could work today without any changes
in Coder. Sorry for the noise!
Implementing a keepalive system that works with
`ServerAliveInterval` from SSH clients and having an option to
ping from the server as well (ala `ClientServerInterval`) would
make sense to me.
|
This was referenced Jun 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related: gliderlabs/ssh#12
Related: #7512
Introducing the default max timeout in #7532 impaired the SSHJ client used by VS Code extension that expects an idle connection. The goal of this issue is to implement the Keep-Alive ping-pong mechanism on the Coder SSH server side so that users with Max Timeout can still use the VS Code extension.
The text was updated successfully, but these errors were encountered: