[tavilach]

I'm not sure which category this belongs to, if any, so I'm posting it in the lounge:

I've had no problem remotely connecting into the CS servers at Berkeley, via the Terminal (SSH). However, I'm on spring break now, and a strange problem occurs when I'm connected. If I let a terminal window sit for just a minute, and then come back to it, it's frozen, and I have to reconnect. It's extremely hard to get my work done like this, as I usually have multiple Terminal windows open, and I often let them sit there for a while. Does anyone know what this problem stems from? I've been connected via Comcast, and a wireless router. I tried using an ethernet cable instead of the wireless, but that doesn't seem to help. Suggestions?

[residentEvil]

hmmm, i know there is a 'keepalive' option on ftp clients, to keep the remote from closing idle sessions. does SSH have such a thing from terminal?

[tavilach]

Originally posted by residentEvil:
hmmm, i know there is a 'keepalive' option on ftp clients, to keep the remote from closing idle sessions. does SSH have such a thing from terminal?

I just tried uncommenting that feature from the sshd_config file, as well as adding clientaliveinterval 30 and clientalivecountmax 999999. No luck .

[ChrisF]

sshd_config only affects the ssh server on your computer. You want to be editing ssh_config (also in /etc) to change options on your ssh client (which is what you'd be using to connect to the remote server.)
I should add that it's likely your problem is due to the configuration of the remote machine rather than yours. The default config isn't going to time out your connections.