Shulou(Shulou.com)06/03 Report--

What is the reason why TIME-WAIT has to wait for 2MLS? In view of this problem, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

TIME-WAIT must wait for 2MLS because waiting for 2MLS can ensure that the last message segment of the client can reach the server. If not, the server will time out to retransmit the connection release message segment, so that both the client and the server can enter the CLOSE shutdown state normally.

TIME-WAIT is a TCP state. Waiting for 2MLS can ensure that the last message segment of the client can reach the server. If not, the server will time out to retransmit the connection release message segment, so that both the client and the server can enter the CLOSE state normally.

Related introduction:

TIME-WAIT is a TCP state.

The start time of time-wait is the state in which the connection party actively closes the connection party after sending the last wave, that is, after the end of the ACK=1 signal.

Then the duration of time-wait is 2MSL. MSL is Maximum Segment Lifetime, translated as "maximum message survival time", which can be 30s 2min or 1min. 2msl is twice as long as this. In engineering, 2msl is 4min. However, it is generally determined according to the actual network situation.

The answer to the question about why TIME-WAIT has to wait for 2MLS is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.