Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem - neither endpoint will notice that anything was wrong. They help if you have a firewall which drops your connection after an idle period but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. Note that keepalives are not always helpful. The value is measured in seconds so, for example, if your firewall cuts connections off after ten minutes then you might want to enter 300 seconds (5 minutes) in the box. If you find your firewall is cutting idle connections off, you can try entering a non-zero value in this field. The keepalive option (‘Seconds between keepalives’) allows you to configure PuTTY to send data through the session at regular intervals, in a way that does not disrupt the actual terminal session. This can cause PuTTY sessions to be unexpectedly closed by the firewall if no traffic is seen in the session for some time. Usually, these firewalls will assume a connection is dead if no data is transferred in either direction after a certain time interval. Some network routers and firewalls need to keep track of all connections through them. If you find your sessions are closing unexpectedly (most often with ‘Connection reset by peer’) after they have been idle for a while, you might want to try using this option. Previous page next page 4.13.1 Using keepalives to prevent disconnection
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |