Solve the problem of automatic disconnection after ssh is idle for a period of time

Use a client tool, such as securecrt, to connect to a linux server. some of them may be disconnected after a period of time without any operation. This is mainly because the vro and firewall exist between the client and the server, and the idle connection will be disconnected after the specified time for its own security. Or the server is set to disconnect idle connections. There are two solutions: one is to start from the server, and the other is to start and release the client tool. Modify/etc/ssh/sshd_config on the server

Use a client tool, such as securecrt, to connect to a linux server. some of them may be disconnected after a period of time without any operation. This is mainly because the vro and firewall exist between the client and the server, and the idle connection will be disconnected after the specified time for its own security. Or the server is set to disconnect idle connections. There are two solutions: one is to start from the server, and the other is to start and release the client tool.

• Server

Modify the ClientAliveInterval 300 (default value: 0) in the/etc/ssh/sshd_config configuration file. the parameter indicates that the server sends a message to the client every five minutes to maintain the connection, use service sshd reload to make the modification take effect. If the problem persists, set 300 to a smaller value, for example, 60.

• Client Tools

Securecrt settings:Session options?> Terminal?> Anti-idle?> Select the Send Protocol NO-OP (p) every 60 seconds

Putty setting method:Putty-> Connection-> Seconds between keepalives (0 to turn off). The default value is 0, which is changed to 300.