I have already written about how to deny or access to users using OpenSSH. Today I am going to write about another interesting problem.
Basically this is a security feature. Ssh connection freezes or drops out after N minutes of inactivity. According to official OpenSSH man page:
"This is usually the result of a packet filter or NAT device timing out your TCP connection due to inactivity. For security, reason most enterprises only use SSH protocol version 2. This problem only occurred with version 2."
If you work for long hours using ssh and left workstation for some other work, your connection will be dropped by remote server. This may be little annoying to you. So to get rid of this problem:
Open your /etc/ssh/sshd_config file:
# vi /etc/ssh/sshd_config
Modify setting as follows:
ClientAliveInterval 30
ClientAliveCountMax 5
Where,
- ClientAliveInterval: Sets a timeout interval in seconds (30) after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The default is 0, indicating that these messages will
not be sent to the client. This option applies to protocol version 2 only. - ClientAliveCountMax: Sets the number of client alive messages (5) which may be sent without sshd receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session.
Close and save the file. Restart sshd:
# /etc/init.d/ssh restart
OR
# service sshd restart
Another option is enable ServerAliveInterval in the client's (your workstation) ssh_config file.
# vi /etc/ssh/ssh_config
Append/modify values as follows:
ServerAliveInterval 15
ServerAliveCountMax 3
Where,
- ServerAliveInterval : Sets a timeout interval in seconds after which if no data has
been received from the server, ssh will send a message through the encrypted channel to request a response from the server.
In above example, ServerAliveInterval is set to 15 and ServerAliveCountMax is left at the 3, if the server becomes unresponsive, ssh will disconnect after approximately 45 seconds. Again this option applies to protocol version 2 only.
Read the man pages of ssh, sshd and sshd_config/ssh_config for more information.
Featured Articles:
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- Linux: 20 Iptables Examples For New SysAdmins
- My 10 UNIX Command Line Mistakes
- 25 PHP Security Best Practices For Sys Admins
- The Novice Guide To Buying A Linux Laptop
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- Top 20 OpenSSH Server Best Security Practices
- Top 10 Open Source Web-Based Project Management Software
Facebook it - Tweet it - Print it -
We're here to help you make the most of sysadmin work. So, subscribe!
{ 4 comments… read them below or add one }
Hey thanks for this article, it was very helpful. I was not aware this problem only occurred with protocol v2 which any one serious about security will be using.
I have found setting the options on the server works best if using a good connection, but otherwise it’s much better to set on the client workstation.
Mac users wishing to edit their workstation configuration should open up terminal and issue the command sudo vi /etc/ssh_config entering your account password when requested. Then just type :wq to save and quit. Sorted.
If you’re on a machine where you don’t have root access, add the following lines to make your connections stay alive:
Host *
ServerAliveInterval 240
Correction:
If you’re on a machine where you don’t have root access, add the following lines to ~/.ssh/config to make your connections stay alive:
Host *
ServerAliveInterval 240
Tried all of the above. After about 3 minutes I loose my connection to the server. GoDaddy is my provider any additional thoughts?