connection timing out

equivariant

A bit of a noob question.

I have a letshost VPS (running Ubuntu 11.10) that I am using to learn about web programming. My problem is that if a terminal is left inactive for about 10 minutes it disconnects, which is annoying as I like to keep 3 or 4 shells
open, but some of them I only need to use infrequently. I know that this
is not a problem with my ssh client as I don't experience this problem on
other servers. Is this something that I can easily fix - is there some setting
that determines how long a shell can be inactive for?

Giuseppe90

What are you using to connect ? If you are connecting from a linux box you could add the following to your /etc/ssh/ssh_config

ServerAliveInterval 60

This will send a message to the server if no data has been received in 60 seconds and should keep your connection active

equivariant

Giuseppe90 wrote: »

What are you using to connect ? If you are connecting from a linux box you could add the following to your /etc/ssh/ssh_config

ServerAliveInterval 60

This will send a message to the server if no data has been received in 60 seconds and should keep your connection active

Thanks.
Sometimes I connect from a linux box, sometimes using putty on my w*****s laptop

Giuseppe90

In the "Connection" section of your putty settings there should be an option to send null packets - change that from 0 to 60 and that should do it. You will need to do that and save for each session you have saved.

Hope that helps

equivariant

Giuseppe90 wrote: »

What are you using to connect ? If you are connecting from a linux box you could add the following to your /etc/ssh/ssh_config

ServerAliveInterval 60

This will send a message to the server if no data has been received in 60 seconds and should keep your connection active

Actually I just realised that if I put

ClientAliveInterval 60

in sshd_config on the server then this sorts the problem from the server side, so I don't have to configure the clients individually