Etant actuellement connecté via une connexion wifi plutôt instable avec mon mac (est-ce lié?), j’avais souvent des freezes de ssh.. et il n’y a rien de pire que devoir tout reprendre a zéro. Et en feuilletant le manpage de sshd_config j’ai trouvé deux paramètres bien sympathiques qui ont résolu mon problème.
/etc/ssh/sshd_config ou /home/$USERNAME/.ssh.config
1 2 | ClientAliveInterval 30 ClientAliveCountMax 5 |
ServerAliveInterval
Sets a timeout interval in seconds after which if no data has been received from the server, ssh(1) will send a message through the encrypted channel to request a response from the server. The default is 0, indicating that these messages will not be sent to the server. This option applies to protocol version 2 only.ServerAliveCountMax
Sets the number of server alive messages (see below) which may be sent without ssh(1) receiving any messages back from the server. If this threshold is reached while server alive messages are being sent, ssh will disconnect from the server, terminating the session. It is important to note that the use of server alive messages is very different from TCPKeepAlive (below). The server alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The server alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.
The default value is 3. If, for example, ServerAliveInterval (see below) is set to 15 and ServerAliveCountMax is left at the default, if the server becomes unresponsive, ssh will disconnect after approximately 45 seconds. This option applies to protocol version 2 only.
Si cela ne fonctionne toujours pas, il vous reste AutoSSH…
