Date: Mon, 21 Mar 2005 14:30:14 -0500 From: Charles Swiger <cswiger@mac.com> To: Robert Gogolok <robertgogolok@web.de> Cc: freebsd-questions@freebsd.org Subject: Re: FIN_WAIT_2 Message-ID: <a4ea0446f316eef2d1eccd68bd552878@mac.com> In-Reply-To: <423F17D9.70802@web.de> References: <423EFE41.6040805@web.de> <56b90b3668acea792519e1e70a7b837a@mac.com> <423F05F2.3010101@web.de> <7c82a2d1780970b84810aefc59bdb295@mac.com> <423F17D9.70802@web.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 21, 2005, at 1:52 PM, Robert Gogolok wrote: > I've looked at the "Closing a Connection" chapter from the RFC and > tried to understand it. The state diagram above shows that from the > FINWAIT-2 state there is only one possible way to reach TIME WAIT. That's right. > So FreeBSD must be using another extension of the RFC-793, when it's > sending ACK messages in the FINWAIT-2 state? If the TCP connection is in FIN_WAIT_2, FreeBSD may send out ACKs periodicly, trying to nudge the other side to send a FIN to finish closing the connection. That may be controlled by the keepalive sysctl, but we're starting to go beyond my specific knowledge. One of the true FreeBSD network wizards like Andre Oppermann might be able to provide more information. > Wow, I'm confused at this point, I have a linux box here which was the > previous webserver, and I can't remember seeing ACK's hitting the > firewall logs as it is now with the FreeBSD webserver. Hmm, it's hard to say. Having a complete tcpdump of a TCP connection handy would help, as would making sure that your firewall rules aren't doing something to interrupt or block the end of the connection. Are you getting any responses back from the clients, or have they disappeared? -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a4ea0446f316eef2d1eccd68bd552878>