From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:20:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE4B316A4CE; Wed, 21 Jul 2004 17:20:35 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A1F43D39; Wed, 21 Jul 2004 17:20:35 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i6LHKOxE045205; Wed, 21 Jul 2004 10:20:28 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200407211720.i6LHKOxE045205@gw.catspoiler.org> Date: Wed, 21 Jul 2004 10:20:24 -0700 (PDT) From: Don Lewis To: dmp@bitfreak.org In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: matt+list.sw.freebsd.current@publicly.neglect.us cc: freebsd-current@FreeBSD.org cc: rwatson@FreeBSD.org Subject: Re: fetch hangs, part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 21 Jul 2004 17:20:36 -0000 On 21 Jul, Darren Pilgrim wrote: >> From: Robert Watson [mailto:rwatson@freebsd.org] >> >> >> On Tue, 20 Jul 2004, Darren Pilgrim wrote: >> >> > I've been having the same (or a similar problem). Fetching the distfile >> > for a port will hang. I poked some more at this and found that all the >> > sites fetch is hanging on successfully negotiate the TCP connection then >> > go dead without closing the connection. My workaround has been to edit >> > the Makefile and remove the offending site from MASTER_SITES or manually >> > fetch from ftp.freebsd.org. >> >> Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? > >> and see if things "get better"? It's one >> of the things that has changed in the TCP code recently. This could well >> be a user space fetch issue, but it would be worth trying it to see, if >> only to rule it out. > > It didn't change. The connections still hung. Smells somewhat like a broken path MTU discovery problem. There might be a hop in the path with a smaller than expected MTU and something between there and the server that is filtering ICMP. An interesting experiment would be to see what happens if a smaller than normal MSS is requested. This would probably be easiest for someone with a PPP connection.