From owner-freebsd-net@freebsd.org Thu Nov 5 15:38:11 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69BFEA277A4 for ; Thu, 5 Nov 2015 15:38:11 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 729E31E32; Thu, 5 Nov 2015 15:38:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA06994; Thu, 05 Nov 2015 17:38:07 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZuMc1-0006O9-OM; Thu, 05 Nov 2015 17:38:05 +0200 Subject: Re: who uses this port? To: Matthew Seaman , freebsd-net@FreeBSD.org References: <563A5F39.7010906@FreeBSD.org> <563B0922.9030805@FreeBSD.org> <563B285A.4070808@freebsd.org> From: Andriy Gapon Message-ID: <563B77A5.4060403@FreeBSD.org> Date: Thu, 5 Nov 2015 17:37:09 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <563B285A.4070808@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 15:38:11 -0000 On 05/11/2015 11:58, Matthew Seaman wrote: > On 05/11/2015 09:20, Ben Woods wrote: >>> I'm more curious as to why sockstat gives you question marks instead of the >>>> proper process details. Any ideas? > > This indicates a connection that is in the process of closing down but > the system still hasn't cleared up all the connection state yet. It's > normal. You might find that adjusting the > net.inet.tcp.fast_finwait2_recycle sysctl makes these old entries get > cleared more promptly. The thing is that the system was in that state for about 10 minutes after which I grew impatient and rebooted it. To me 10 minutes seem like more than plenty of time even for the slow algorithm. -- Andriy Gapon