Differences between version 4 and revision by previous author of TcpStates.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, March 23, 2005 3:50:48 pm | by JohnMcPherson | Revert |
| Older page: | version 3 | Last edited on Thursday, October 9, 2003 1:17:24 pm | by DiegoBohman | Revert |
@@ -10,4 +10,24 @@
;LAST_ACK:A FIN has been received, we've sent our own FIN, but we are waiting on the ACK before we can move to the closed state.
;FIN_WAIT_1:A FIN has been sent, waiting for a ACK or FIN
;FIN_WAIT_2:A FIN has been sent, and an ACK has been received. More data can be received. This connection is half open.
;CLOSING:A FIN has been sent, and one received, the FIN hasn't been ACK'd yet.
+
+----
+The amount of time that a connection waits in various stages is controlled by the OperatingSystem. Some OS'es let you tune these settings. For example, for Linux-based OSes, look in /proc/sys/net/ipv4.
+
+From /usr/src/linux/Documentation/filesystems/proc.txt:
+
+tcp_syn_retries:
+ Number of times initial SYNs for a TCP connection attempt will be retransmitted. Should not be higher than 255. This is only the timeout for outgoing connections, for incoming connections the number of retransmits is defined by tcp_retries1.
+
+tcp_fin_timeout:
+ The length of time in seconds it takes to receive a final FIN before the
+ socket is always closed. This is strictly a violation of the TCP
+ specification, but required to prevent denial-of-service attacks.
+
+tcp_retries1:
+ Defines how often an answer to a TCP connection request is retransmitted
+ before giving up.
+
+tcp_retries2:
+ Defines how often a TCP packet is retransmitted before giving up.
