Superhub : Telnet / SSH connection dying

[One Pound]

I'm using SSH to remote connect into a server, previously did the same using telnet. I've found that after about 10 minutes that the connection hangs and I need to reconnect.

This is quite annoying as I often might need to do some work on my own PC then switch to the remote server and find the connection has failed.

Is this perhaps down to the Superhub not liking long connections that might remain idle for a long time? Should I switch to modem mode.

[General Maximus]

yeah, peeps have had this problem before. There is a default timeout setting in the shub which is a little bit too sensitive and unfortunately you cant change it

[Chrysalis]

only 2 ways round it.

use modem mode

or force frequent keepalive packets on the ssh session.

[djb61]

Depending on the client software you may be able to work around it by sending keepalive packets as the previous poster stated.

E.g. in putty simply go to Connection settings, tick "Enable TCP keepalives" and set an appropriate interval (I have mine set to 10 seconds). With this configuration against my sessions in putty I no longer have any issues with idle sessions being dropped by the superhub.

[One Pound]

Ahh, thanks. There is a keep-alive setting; I'll try setting it to 60 secs