Date: Fri, 27 Jun 2008 14:27:20 -0400 From: Paul <paul@gtcomm.net> To: Eygene Ryabinkin <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... Message-ID: <48653108.4080806@gtcomm.net> In-Reply-To: <cApEDKk3Lgor00nO3MwN6FQbgGQ@ueg2etH2tHnUpbLg646csVJgCAY> References: <486283B0.3060805@transip.nl> <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc> <48648D70.50304@transip.nl> <c9uXVuSzhJDd2VY%2Bhw9uuGe5NAg@3xQSkDAynh8xLl8Q/P9pjshN3Fo> <4864E0FE.40708@gtcomm.net> <cApEDKk3Lgor00nO3MwN6FQbgGQ@ueg2etH2tHnUpbLg646csVJgCAY>
next in thread | previous in thread | raw e-mail | index | archive | help
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;'? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48653108.4080806>