From owner-freebsd-net@FreeBSD.ORG Fri Jun 27 18:25:22 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 F0A16106567F for ; Fri, 27 Jun 2008 18:25:22 +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 D65298FC0A for ; Fri, 27 Jun 2008 18:25:22 +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 1KCIaF-0002LM-Pv; Fri, 27 Jun 2008 14:22:07 -0400 Message-ID: <48653108.4080806@gtcomm.net> Date: Fri, 27 Jun 2008 14:27:20 -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> <4864E0FE.40708@gtcomm.net> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: rwatson@freebsd.org, 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 18:25:23 -0000 Hi Eygene.. It happens with telnet :) A lot of my closed entries are from telnet so I can't really put a finger on any specific application :/ Eygene Ryabinkin wrote: > Paul, good day. > > Fri, Jun 27, 2008 at 08:45:50AM -0400, Paul wrote: > >> 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. >> > > And what is listening to that port? Can you identify the application? > Just for the record -- may be it will narrow down the search list. > > Robert Watson told us today at the morning that he spotted the bug > that lead to the '*' instead of port number. Robert, can you post > the patch -- it seems to be not yet committed, at least cvs-src > list has no signs of it? > > By the way, is the patch touches in_pcbdrop() in /sys/netinet/in_pcb.c, > removing instruction 'inp->inp_lport = 0;'? >