From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 13:51:06 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8229016A417 for ; Fri, 21 Sep 2007 13:51:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 715B313C45A for ; Fri, 21 Sep 2007 13:51:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 204631CC02A; Fri, 21 Sep 2007 06:33:16 -0700 (PDT) Date: Fri, 21 Sep 2007 06:33:16 -0700 From: Jeremy Chadwick To: Petr Holub Message-ID: <20070921133316.GA63294@eos.sc1.parodius.com> References: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@freebsd.org Subject: Re: TCP socket problem on Sept. -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 13:51:06 -0000 On Fri, Sep 21, 2007 at 01:49:19PM +0200, Petr Holub wrote: > Hi, > > I've encountered the following problem while building xorg from > ports: > > TCP: [134.76.12.3]:21 to [147.251.54.186]:56914 tcpflags 0x18; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:62424 tcpflags 0x18; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:55989 tcpflags 0x18; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:52923 tcpflags 0x18; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > > It occurred from several different addresses and results in being > unable event to ping that IP until reboot. This is "normal" for the current time being, as the output in question is being used to help track down a TCP-related bug in -CURRENT: http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075984.html If the log messages annoy you, set the following sysctl. net.inet.tcp.log_debug=0 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |