[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: Robert Watson <rwatson_(_at_)_FreeBSD_(_dot_)_org>
- Date: Fri, 27 Jun 2008 19:33:30 +0100 (BST)
- Cc: net_(_at_)_freebsd_(_dot_)_org, Ali Niknam <freebsd-net_(_at_)_transip_(_dot_)_nl>, Paul <paul_(_at_)_gtcomm_(_dot_)_net>
On Fri, 27 Jun 2008, 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
126.96.36.199.* 188.8.131.52.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;'?
I've not yet had a chance to put the patch together; it does involve removing
that line, but it's somewhat more complicated because inp_lport is used to
signal whether or not the inpcb is still in various linked list. My current
thinking is that I'd actually like to make it an explicit flag that indicates
being on the lists so that we can have the port set non-zero yet no longer be
on the lists (which would cause the closed connection to occupy the tuple).
Robert N M Watson
University of Cambridge
freebsd-net_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe_(_at_)_freebsd_(_dot_)_org"