From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 19:03:41 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 58B1516A4AB for ; Fri, 21 Sep 2007 19:03:41 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 646AA13C459; Fri, 21 Sep 2007 19:03:40 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F4158D.6030208@FreeBSD.org> Date: Fri, 21 Sep 2007 21:03:41 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Petr Holub References: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> In-Reply-To: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit 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 19:03:41 -0000 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. These log messages are informational, if you see ICMP problems it must have another source. Kris