Date: Tue, 28 Sep 1999 18:30:02 -0700 (PDT) From: "Rob Wise" <rob@ideal.net.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/14026: Many network connections get left in the 'CLOSING' state Message-ID: <199909290130.SAA48894@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/14026; it has been noted by GNATS. From: "Rob Wise" <rob@ideal.net.au> To: "Garrett Wollman" <wollman@khavrinen.lcs.mit.edu> Cc: <freebsd-gnats-submit@FreeBSD.ORG> Subject: Re: kern/14026: Many network connections get left in the 'CLOSING' state Date: Wed, 29 Sep 1999 11:26:34 +1000 ----- Original Message ----- From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: <rob@ideal.net.au> Cc: <freebsd-gnats-submit@FreeBSD.ORG> Sent: Wednesday, September 29, 1999 11:01 AM Subject: kern/14026: Many network connections get left in the 'CLOSING' state > <<On Tue, 28 Sep 1999 16:16:06 -0700 (PDT), rob@ideal.net.au said: > > > tcp 0 0 proxy1.syd.8080 port19.syd.2197 CLOSING > > tcp 0 0 proxy1.syd.8080 port56.cam.1779 CLOSING > > Sorry, that's Just The Way TCP Works. In particular, this can happen > if the client completely disconnects from the network at an > inopportune moment.(*) Eventually TCP will send a probe to that address > while some other user is connected; when this happens, the other end > will reply with a reset and the state for this connection will be > zapped. How often are these probes supposed to be sent? Some of these connections have been around for well over a month. I've started a tcpdump on one of the hosts with a 'CLOSING' connection open and I'll see what happens. Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909290130.SAA48894>