From owner-freebsd-questions@FreeBSD.ORG Mon Jun 16 20:48:41 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CEC21065675 for ; Mon, 16 Jun 2008 20:48:41 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id 327D38FC12 for ; Mon, 16 Jun 2008 20:48:41 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 7FC2928447; Mon, 16 Jun 2008 16:48:40 -0400 (EDT) To: Agus References: From: Lowell Gilbert Date: Mon, 16 Jun 2008 16:48:40 -0400 In-Reply-To: (Agus's message of "Sat\, 14 Jun 2008 16\:11\:31 -0300") Message-ID: <44myllw1g7.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: User Questions Subject: Re: Doubt about hanged ESTABLISHED connections on netstat... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 20:48:41 -0000 Agus writes: > Today i was on my Freebsd6.1 logged from my notebook through SSH...somehow i > lost my Internet connection on my laptop; i realized that, cause i couldnt > type anything on ssh so i checked and i had lost internet connection....I > reset my router..connect through Internet, now working, to my BSD again and > i can see the old connections as ESTABLISHED.....They are hanged there cause > of the loss of my connection i guess....So my doubt and question was; > Is this normal behaviour, who is "in charge" of managing this? the TCP > stack, or can i config SSH...If someone who's got the time and willing to > explain, share thoughts about this, i ll be grateful... They will time out when the application tries to send some data and fails for a period of time. You can configure ssh to use "keepalives" if you want to hurry this along. Or you can kill the process holding the socket, and the socket will be closed along with the process. It isn't something to spend time worrying about unless you really want to...