Solution to idle disconnection due to ssh connection timeout

How can I avoid idle ssh connection due to timeout? During SSH connection, the server is often kicked out without operation for a long time. the common prompt is Writefailed: Brokenpipe. if there are countless SSH connections for a while... how can I avoid idle ssh connection due to timeout? During SSH connection, the server is often kicked out after a long period of time without operation. common tips: Write failed: broken pipe this is because if there is no data transmission on the SSH connection for a period of time, the connection will be disconnected. There are two ways to solve this problem. Solution 1: The setting method on the client is very simple. you only need to edit (root permission required)/etc/ssh/ssh_config on the client computer and add the following line: serverAliveInterval 60 and later, when a user in the system connects to SSH, a KeepAlive request is sent every 60 seconds to avoid being kicked. Solution 2: If you have the required permissions on the server, you can also set them on the linux server, that is, edit/etc/ssh/sshd_config and add: clientAliveInterval 60 after the SSH server is restarted, this setting takes effect. Each client connected to this server is affected. It should be noted that after this function is enabled, security will decrease.