From owner-freebsd-net@FreeBSD.ORG  Fri Jun 27 14:06:22 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 404251065672;
	Fri, 27 Jun 2008 14:06:22 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45])
	by mx1.freebsd.org (Postfix) with ESMTP id ECDD18FC1A;
	Fri, 27 Jun 2008 14:06:21 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru;
	h=Received:Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender;
	b=QZHH2vstl7U5H4NSQRPPTNq6NSL+BX6klR0BA0WnTstN5rspAeqU1Ru5dOt465WPu0JV2AvUOlWwWwA/Y+a+/UxU+upc9q/3cmt5AIGJ9LlMIEpBig8hzi7bycBv29FG6WxtTGT3OiHrMmn+h5FpOefug/K74kwjgyHDkwggKxo=;
Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25])
	by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256)
	id 1KCEai-000FNA-KJ; Fri, 27 Jun 2008 18:06:20 +0400
Date: Fri, 27 Jun 2008 18:06:19 +0400
From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: Paul <paul@gtcomm.net>
Message-ID: <cApEDKk3Lgor00nO3MwN6FQbgGQ@ueg2etH2tHnUpbLg646csVJgCAY>
References: <486283B0.3060805@transip.nl>
	<5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc>
	<48648D70.50304@transip.nl>
	<c9uXVuSzhJDd2VY+hw9uuGe5NAg@3xQSkDAynh8xLl8Q/P9pjshN3Fo>
	<4864E0FE.40708@gtcomm.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <4864E0FE.40708@gtcomm.net>
Sender: rea-fbsd@codelabs.ru
Cc: rwatson@freebsd.org, Ali Niknam <freebsd-net@transip.nl>, 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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2008 14:06:22 -0000

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;'?
-- 
Eygene

Remember that it is hard to read the on-line manual while single-stepping
the kernel.  -- FreeBSD Developers handbook