Date: Mon, 21 Mar 2005 18:35:46 +0100 From: Robert Gogolok <robertgogolok@web.de> To: Charles Swiger <cswiger@mac.com> Cc: freebsd-questions@freebsd.org Subject: Re: FIN_WAIT_2 Message-ID: <423F05F2.3010101@web.de> In-Reply-To: <56b90b3668acea792519e1e70a7b837a@mac.com> References: <423EFE41.6040805@web.de> <56b90b3668acea792519e1e70a7b837a@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Charles Swiger wrote: > The TCP stack wants the remote end to acknowledge the last FIN it sends > and close the connection cleanly, and there is a timer (2 * MSL?) which > gets started when a connection moves into the closing stages > (FIN_WAIT_1, FIN_WAIT_2, LAST_ACK). So FIN_WAIT_2 is the time the server waits to receive the FIN from the client, but although it doesn't get this last FIN message yet, it sends ACK's for the expected FIN message? > It's not uncommon for some clients (think dialup users running Win98), > to drop the connection rather rather than close it properly. So the client has time to ACK the server's FIN, but the user closes the dialup connection, so the application hasn't sent the FIN? > Your system should time out these connections after a while. Good decision:-) Greetings, Robert!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?423F05F2.3010101>