Timeline for Why TCP TIME-WAIT State is present at both ends after a connection termination?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2013 at 15:53 | comment | added | Vangelis Tasoulas | According to this en.wikipedia.org/wiki/File:TCP_CLOSE.svg one end will initiate the termination (active end) of a connection and only this will go through the TIME-WAIT state. The passive end should just close it. The same is what I see in different books as well. Do I miss something here? | |
| Mar 10, 2013 at 15:49 | comment | added | vonbrand | TCP connections have data flowing in both directions. | |
| Mar 10, 2013 at 15:41 | comment | added | Vangelis Tasoulas | I read this, but the question is about why I see the TIME-WAIT state to both ends. This state should only be there in the node initiated the connection termination and not the other one (according to what I read so far). | |
| Mar 10, 2013 at 15:33 | history | answered | vonbrand | CC BY-SA 3.0 |
