From owner-freebsd-bugs Tue Sep 28 18:30: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7EFEE15885 for ; Tue, 28 Sep 1999 18:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA48894; Tue, 28 Sep 1999 18:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 28 Sep 1999 18:30:02 -0700 (PDT) Message-Id: <199909290130.SAA48894@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Rob Wise" Subject: Re: kern/14026: Many network connections get left in the 'CLOSING' state Reply-To: "Rob Wise" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/14026; it has been noted by GNATS. From: "Rob Wise" To: "Garrett Wollman" Cc: 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 To: Cc: Sent: Wednesday, September 29, 1999 11:01 AM Subject: kern/14026: Many network connections get left in the 'CLOSING' state > < > > 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