TIME_WAIT state as long as it is each time? Close to the active implementation of a book that it must end after TIME_WAIT state. Would like to ask the state of the environment is the same as long? There are similar "in a very short time under normal circumstances, time is 2MSL exceptional circumstances" such an argument? I encountered the problem is that client server close to the first, and then the server immediately started again, this time at Port listen and TIME_WAIT state, listen and failure. TIME_WAIT state must wait until (my environment is one minute) will continue to listen and beyond (but sure) This is a normal phenomenon? We have to wait TIME_WAIT Mody, it is impossible to immediately start again? TIME_WAIT state as long as it is each time? Some places. TIME_WAIT state as long as it is each time? You can listen and re-installed socket rather than wait for the property. If not listen and the state port, you can listen and. The following cases : Int yes=1; Setsockopt (fd, SOL_SOCKET, SO_REUSEADDR, &yes, sizeof (struct sockaddr)); TIME_WAIT state as long as it is each time? As long as it can listen and listen and state? No bar : : TIME_WAIT because of the role is to prevent wandering inside one of the packages on the Internet under a listen and have an impact on the bars (I understand this may be wrong : :) If this is the case TIME_WAIT state failure will listen and bars, even if it is not a state LISTEN Just put setsockopt added tried it, or not ah TIME_WAIT state as long as it is each time? 55555555, is sorry ah : : I was mistaken, I thought I was in the wrong listen and when, in fact, bind when it failed : : However, the reasons should be no distinction, because TIME_WAIT state (Is this wrong, -) (Just read the postings samuelz (Socket Binding), I found the same problem seems to be returning to bind themselves a try -- indeed the wrong time) TIME_WAIT state as long as it is each time? Pasini reason, TCPv1 have to explain. SERVER : While we should be active implementation send FIN section, the terminal awaiting peer ACK, to the occupation of the port resources. 2MSL should understand is that different OS MSL different sizes. In this 2MSL Server no longer activated. TIME_WAIT state as long as it is each time? Thank you narkissos, and albcamus! samuelz ! ! Solve the basic problem : LISTEN tcp 0 0 *:9999 *:* Tcp 0 0 10.71.55.10:9999 testsvr-3s6:51594 TIME_WAIT Tcp 0 0 10.71.55.10:9999 10.64.32.135:44935 TIME_WAIT Tcp 0 0 10.71.55.10:9999 10.64.32.135:44942 ESTABLISHED Tcp 0 0 10.71.55.10:9999 testsvr-3s6:51632 ESTABLISHED I just said put setsockopt added to the list or failed, it was because I thought it was in the wrong listen and on, listen and then inserted in the setsockopt, but since then it has failed bind above, operating procedures and not to setsockopt : : sorry! ! Setsockopt in bind add, change attributes SO_REUSEADDR, Server can resume, we can see above TIME_WAIT state is not over, but a new server link has been established Thank you again! TIME_WAIT state as long as it is each time? Wait a moment! You establish a state that the server port, the implementation of the initiative to shut down and then killed. Immediately activated, can be up - I flipped about TCP Comments v1 prove their understanding of the National Taiwan Normal University, she responds : No, in this 2MSL time, the implementation of the initiative to close the service side of the socket pair are unable to use it! TIME_WAIT state as long as it is each time? Yes, yes, ah I netstat-a | grep 9999 (I have to listen and the port) The results set out in the ah I do not think that one has started, but by the whole socket narkissos said after the SO_REUSEADDR option can be changed to a specific principle is not very clear : : Send FIN client server then send ACK sending FIN FIN Client server then accept ACK ACK ACK then send FIN The server does not know when not to send their client's ACK and retry if there is the possibility (for example, received what RST), she will not end, so TIME_WAIT. This time should in principle be allowed in the bar again bind, because they would interfere with the normal end packages : : Setsockopt internal certainly done a lot of work : : TIME_WAIT state as long as it is each time? 2MSL no longer the TIME_WAIT state is not reduced when the original socket is not abandoned TIME_WAIT wait : : [ Closed window ]