TCP KeepAlive: Difference between revisions
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
TCP Keep-Alive is a mechanism that insures small probe packets are periodically sent to the other end of the TCP connection. An ACK response is expected for each packet. Under normal circumstances, if the TCP Keep-Alive is enabled and if the TCP stacks at both ends are up, the connection will stay up indefinitely, regardless of whether the application layers at both ends send data or stay idle. | TCP Keep-Alive is a mechanism that insures small probe packets are periodically sent to the other end of the TCP connection. An ACK response is expected for each packet. Under normal circumstances, if the TCP Keep-Alive is enabled and if the TCP stacks at both ends are up, the connection will stay up indefinitely, regardless of whether the application layers at both ends send data or stay idle. The keep-alive probe logic is implemented in the TCP stack. Since ACK will only be returned if the other end of the connection is reachable and alive, the lack of acknowledgment is interpreted as failure and, after some retries, the OS will close the TCP end-point and will release the associated resources. The application listening on that particular socket will receive an error from the OS. | ||
Aside from application notification in case of connection failure, another benefit of enabling TCP Keep-Alive is that it keeps the connection "active" so if the connection goes over a firewall that watches for inactivity, that will prevent the firewall from dropping the connection. | |||
The keep-alive protocol is implemented with a keepalive packet, which contains contains null data. In an Ethernet network, a keepalive frame length is 60 bytes, while the server response to this, also a null data frame, is 54 bytes. | |||
=Configuration= | =Configuration= | ||
Revision as of 00:21, 26 July 2018
External
Internal
Overview
TCP Keep-Alive is a mechanism that insures small probe packets are periodically sent to the other end of the TCP connection. An ACK response is expected for each packet. Under normal circumstances, if the TCP Keep-Alive is enabled and if the TCP stacks at both ends are up, the connection will stay up indefinitely, regardless of whether the application layers at both ends send data or stay idle. The keep-alive probe logic is implemented in the TCP stack. Since ACK will only be returned if the other end of the connection is reachable and alive, the lack of acknowledgment is interpreted as failure and, after some retries, the OS will close the TCP end-point and will release the associated resources. The application listening on that particular socket will receive an error from the OS.
Aside from application notification in case of connection failure, another benefit of enabling TCP Keep-Alive is that it keeps the connection "active" so if the connection goes over a firewall that watches for inactivity, that will prevent the firewall from dropping the connection.
The keep-alive protocol is implemented with a keepalive packet, which contains contains null data. In an Ethernet network, a keepalive frame length is 60 bytes, while the server response to this, also a null data frame, is 54 bytes.
Configuration
There are three parameters related to keepalive:
Keepalive time
The time of connection inactivity after which the first keep alive request is sent. In other words, is the duration between two keepalive transmissions in idle condition. The default value on Linux is 2 hours (7,200 seconds). More details TCP KeepAlive on Linux.
Keepalive interval
The duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received.
Keepalive retry
The number of retransmissions to be carried out before declaring that remote end is not available.
O/S Specific Details
The fact that TCP KeepAlive is enabled or not, and how it is configured, it is OS-dependent
TCP Keepalive on Linux
- The TCP KeepAlive Source of Record http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/
- Using TCP Keepalive to Detect Network Errors http://www.gnugk.org/keepalive.html
Questions and TODO
- Can keepalive be set per TCP connection, or is a system-wide setting (all TCP/IP connections)?
- So it is true that if I don't have keep alive, my write can block forever if I power off the other end suddenly.