http://hwarf.com/2009/06/24/sshd-idle-timeout/ Random Fri, 22 Jan 2010 18:52:32 +0000 hourly 1 http://wordpress.org/?v=3.0 http://hwarf.com/2009/06/24/sshd-idle-timeout/comment-page-1/#comment-55 Jordan Lev Wed, 06 Jan 2010 20:23:55 +0000 http://hwarf.com/?p=196#comment-55 Thanks for this helpful post! I was having lots of trouble getting this to work for larger amounts of time (30-60 minutes) because I thought these were the settings for the actual timeout limit of the sshd sessions so I was setting the ClientAliveInterval to a very high value (3600 for an hour). BUT I didn't understand that this isn't changing the timeout limit -- those are set elsewhere (not sure where, but it doesn't matter) and seem to be 15 minutes on my Ubuntu Hardy system. What these ClientAlive___ settings do send a packet back and forth to the client every so often to keep the connection alive, so you must set the ClientAliveInterval to a number that is LOWER than whatever the built-in timeout is (so in my case, less than 900 [900 seconds=15 minutes]), then set the ClientAliveCountMax to the number of times you want that packet sent. So what worked for me to keep the session alive for an hour was to set both to 60 -- send the packet every 60 seconds, and do that 60 times. Phew! Thanks for this helpful post! I was having lots of trouble getting this to work for larger amounts of time (30-60 minutes) because I thought these were the settings for the actual timeout limit of the sshd sessions so I was setting the ClientAliveInterval to a very high value (3600 for an hour). BUT I didn’t understand that this isn’t changing the timeout limit — those are set elsewhere (not sure where, but it doesn’t matter) and seem to be 15 minutes on my Ubuntu Hardy system. What these ClientAlive___ settings do send a packet back and forth to the client every so often to keep the connection alive, so you must set the ClientAliveInterval to a number that is LOWER than whatever the built-in timeout is (so in my case, less than 900 [900 seconds=15 minutes]), then set the ClientAliveCountMax to the number of times you want that packet sent. So what worked for me to keep the session alive for an hour was to set both to 60 — send the packet every 60 seconds, and do that 60 times. Phew!

]]>