[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FreeBSD 7.0: sockets stuck in CLOSED state...
- To: Eygene Ryabinkin <rea-fbsd_(_at_)_codelabs_(_dot_)_ru>
- Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state...
- From: Paul <paul_(_at_)_gtcomm_(_dot_)_net>
- Date: Fri, 27 Jun 2008 14:27:20 -0400
- Cc: rwatson_(_at_)_freebsd_(_dot_)_org, Ali Niknam <freebsd-net_(_at_)_transip_(_dot_)_nl>, net_(_at_)_freebsd_(_dot_)_org
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 18.104.22.168.* 22.214.171.124.1261 CLOSED
7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #6: Thu Apr 17 18:11:49 EDT 2008
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;'?
freebsd-net_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe_(_at_)_freebsd_(_dot_)_org"