From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 12:52:08 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 1B49A16A469 for ; Fri, 21 Sep 2007 12:52:08 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id 85A8D13C4A3 for ; Fri, 21 Sep 2007 12:52:07 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (kloboucek.ics.muni.cz [147.251.3.38]) (authenticated user=hopet@ICS.MUNI.CZ bits=0) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id l8LBnHvw004823 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 21 Sep 2007 13:49:18 +0200 From: "Petr Holub" To: Date: Fri, 21 Sep 2007 13:49:19 +0200 Message-ID: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Importance: Normal X-Muni-Spam-TestIP: 147.251.3.38 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Envelope-To: current@freebsd.org X-Muni-Virus-Test: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Fri, 21 Sep 2007 13:49:18 +0200 (CEST) X-Mailman-Approved-At: Fri, 21 Sep 2007 13:31:23 +0000 Cc: Subject: 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 12:52:08 -0000 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. Petr