4 way close - Revision history

84.170.212.68 at 17:37, 27 April 2010

2010-04-27T17:37:38Z

← Older revision		Revision as of 10:37, 27 April 2010
Line 13:		Line 13:
	the last ACK gets replied to with an RST.		the last ACK gets replied to with an RST.

	The above closing sequence sees the following states:		The above closing sequence sees the following [[tcp states\|states]]:

	1. Host A = FIN_WAIT1 Host B = ESTABLISHED		1. Host A = FIN_WAIT1 Host B = ESTABLISHED

Pbug at 20:52, 24 March 2008

2008-03-24T20:52:15Z

← Older revision		Revision as of 13:52, 24 March 2008
Line 1:		Line 1:
	To close a [[TCP]] session a four way closing handshake is performed.		To close a [[TCP]] session a four way closing handshake is performed.

	Host A ~~wants to close~~ and sends FIN with seq 1000		1. Host A closes and sends FIN with seq 1000
	Host B ACK's with ack set to 1001		2. Host B ACK's with ack set to 1001
	Host B sends its own FIN with seq 500		3. Host B sends its own FIN with seq 500
	Host A ACK's the last FIN with 501		4. Host A ACK's the last FIN with 501

	The connection is then considered to be closed. The active part of closing (the initiator) keeps a state in TIME_WAIT state for 2MSL ([[MSL]]). Typically		The connection is then considered to be closed. The active part of closing (the initiator) keeps a state in TIME_WAIT state for 2MSL ([[MSL]]). Typically
Line 12:		Line 12:
	has been ACK'ed that the connection is torn down and		has been ACK'ed that the connection is torn down and
	the last ACK gets replied to with an RST.		the last ACK gets replied to with an RST.

			The above closing sequence sees the following states:

			1. Host A = FIN_WAIT1 Host B = ESTABLISHED
			2. Host A = FIN_WAIT2 Host B = CLOSE_WAIT
			3. Host A = TIME_WAIT Host B = LAST_ACK
			4. Host A = TIME_WAIT Host B = CLOSED

			Check with RFC 793 page 23 (diagram 6) for the
			accuracy of this finite state machine.

Pbug: 4 way close

2008-03-24T20:29:50Z

4 way close

New page

To close a [[TCP]] session a four way closing handshake is performed.

Host A wants to close and sends FIN with seq 1000
Host B ACK's with ack set to 1001
Host B sends its own FIN with seq 500
Host A ACK's the last FIN with 501

The connection is then considered to be closed. The active part of closing (the initiator) keeps a state in TIME_WAIT state for 2MSL ([[MSL]]). Typically
this can be observed in a server that has POP3 service. After the client sends the QUIT call the server replies with a +OK and immediately calls close() thus becoming the active closing end.

It's possible (often in windows) that once the FIN
has been ACK'ed that the connection is torn down and
the last ACK gets replied to with an RST.