In TCP networking, what is a FIN_WAIT state?

最新推荐文章于 2024-07-15 11:42:54 发布

macyang

最新推荐文章于 2024-07-15 11:42:54 发布

阅读量764

点赞数

分类专栏： socket 文章标签： tcp networking server application layer

本文链接：https://blog.csdn.net/macyang/article/details/5138656

版权

socket 专栏收录该内容

10 篇文章 0 订阅

订阅专栏

FIN_WAIT_2 seems to occur when the server has an active connection with a client and it wants to shut down the TCP connection (probably in response to a normal application layer "exit"). The server sends the client a packet with a "FIN" bit set. At this point, the server is in FIN_WAIT_1 state. The client gets the FIN packet and goes into CLOSE_WAIT state, and sends an acknowledgment packet back to the server. When the server gets that packet, it goes into FIN_WAIT_2 state. From the server's perspective, the connection is now closed, and the server can't send any more data. However, under the TCP protocol, the client needs to shut down also by sending a FIN packet, which the server TCP implementation should ACK. The server should close about two milliseconds later.

The following diagram is taken from RFC 793 (defining the TCP protocol):

TCP A TCP B 1. ESTABLISHED ESTABLISHED 2. (Close) FIN-WAIT-1 --> <SEQ=100><ACK=300><CTL=FIN,ACK> --> CLOSE-WAIT 3. FIN-WAIT-2 <-- <SEQ=300><ACK=101><CTL=ACK> <-- CLOSE-WAIT 4. (Close) TIME-WAIT <-- <SEQ=300><ACK=101><CTL=FIN,ACK> <-- LAST-ACK 5. TIME-WAIT --> <SEQ=101><ACK=301><CTL=ACK> --< CLOSED 6. (2 MSL) CLOSED

Some clients have faulty TCP implementations, and leave the server hanging in FIN_WAIT_2 state. In particular, this can cause problems

with Indiana University's Unicorn system.