From owner-freebsd-net@FreeBSD.ORG Fri Jun 27 13:02:58 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4467C106566B for ; Fri, 27 Jun 2008 13:02:58 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 290D48FC12 for ; Fri, 27 Jun 2008 13:02:58 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-179-28.hsd1.fl.comcast.net ([76.108.179.28] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KCDFm-00006l-KA; Fri, 27 Jun 2008 08:40:38 -0400 Message-ID: <4864E0FE.40708@gtcomm.net> Date: Fri, 27 Jun 2008 08:45:50 -0400 From: Paul User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Eygene Ryabinkin References: <486283B0.3060805@transip.nl> <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc> <48648D70.50304@transip.nl> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Ali Niknam , net@freebsd.org Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 13:02:58 -0000 I have the same 'problem' if that helps any.. Sockets stuck for over a month in CLOSED and they have a * for the port on the source IP. tcp4 0 0 67.1.1.1.* 67.1.1.2.1261 CLOSED 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #6: Thu Apr 17 18:11:49 EDT 2008 amd64 Doesn't seem to cause any issues though. Eygene Ryabinkin wrote: > Ali, good day. > > Fri, Jun 27, 2008 at 08:49:20AM +0200, Ali Niknam wrote: > >>> Just a quick "me too" message: I also used to see this on my 7.x >>> machines. This was with Apache servers in the proxy setup: one >>> >> I'm wondering: where these 32 bit, or 64 bit machines? >> > > amd64. > > >>> I had already tried to debug this situation and Mike Silbersack >>> helped me with patching the kernel. At that days his patches (that >>> went into 7.x) helped, but with higher request rate to the Apache, >>> they seem to be back again. I can try to setup the testbed and >>> verify if I will still be able to reproduce them. Will it be needed? >>> >>> >> Well, if your machine was indeed 64 bit, I for one would be very >> interested in knowing if it also appears in 32 bit. >> > > Have no i386 machines to test on, sorry. Moreover, I can not yet > reproduce the problem on my amd64, but I am continuing experiments. >