Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- David Deutsch
January 23, 2005, 6:01 am
rate this thread
two (I have already read the man page)? I'm trying to a) keep my NAT from
timing out my connection, and B) terminate the process asap if the NAT
*does* time it out (so that I can detect it and restart the process).
- Richard E. Silverman
January 23, 2005, 6:47 am
Re: Difference between ServerAliveInterval and TCPKeepAlive?
David> Could someone give me a quick explanation of the difference
David> between these two (I have already read the man page)? I'm
David> trying to a) keep my NAT from timing out my connection, and B)
David> terminate the process asap if the NAT *does* time it out (so
David> that I can detect it and restart the process).
TCPKeepAlive is not SSH-specific; it simply sets the "keep-alive" option
on the underlying TCP connection. TCP keepalive is not intended to keep
anything alive, as in avoiding NAT timeouts. Rather, it detects and reaps
half-dead TCP connections to prevent them from building up over time. It
typically operates over too long a time scale to be useful in defeating
NAT timeout, and that scale is usually only tunable for the whole TCP
stack, not per-connection.
ServerAliveInterval controls keepalive messages which are sent within the
SSH protocol; since they are application-level and hence tunable
per-connection, this is what you want to use.
- » Force restrict command on all users except those in a group?
- — Next thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum