From owner-freebsd-stable@FreeBSD.ORG Sun Apr 20 22:39:11 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 615EA1065673 for ; Sun, 20 Apr 2008 22:39:11 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.freebsd.org (Postfix) with ESMTP id E40658FC16 for ; Sun, 20 Apr 2008 22:39:10 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.4/8.13.1) with ESMTP id m3KMd9xO006053; Mon, 21 Apr 2008 00:39:09 +0200 (CEST) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.4/8.13.1/Submit) id m3KMd8UY006052; Mon, 21 Apr 2008 00:39:08 +0200 (CEST) (envelope-from hk) Date: Mon, 21 Apr 2008 00:39:08 +0200 From: Holger Kipp To: Jeremy Chadwick Message-ID: <20080420223908.GA4431@intserv.int1.b.intern> References: <20080418131318.GA27272@intserv.int1.b.intern> <20080420182328.GA99572@intserv.int1.b.intern> <20080420204927.GA52929@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080420204927.GA52929@eos.sc1.parodius.com> User-Agent: Mutt/1.4.2.1i Cc: Holger Kipp , stable@freebsd.org Subject: Re: [FOUND] connection reset after second syn-ack was sent (FreeBSD 7.0) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2008 22:39:11 -0000 On Sun, Apr 20, 2008 at 01:49:27PM -0700, Jeremy Chadwick wrote: > On Sun, Apr 20, 2008 at 08:23:28PM +0200, Holger Kipp wrote: > > Well, still open questions here. Sight. > > Suggestions welcome. Ah, the initiating system is HP-UX... > > I doubt this is the cause, but it's worth asking. > > 1) Are you using pf(4) on the RELENG_7 box at all? No, this is a vanilla 7.0-RELEASE installation with only lpd and ntpd configured. Neither of pf, ipf or ipfw is used. > 2) Have you tried turning off RFC1323 on the RELENG_7 box to see if > the TCP behaviour changes? sysctl net.inet.tcp.rfc1323=0. OK, will do. However, the described problem only happens when the box is resending SYN-ACK after SYN was received and no answer (ACK) was received after the first SYN-ACK. All other connection requests from the same host to the same port (lpd) work without problems. So currently this affects about 0.1 to 0.3 percent of all 3000 - 6000 print requests. Regards, Holger Kipp