Received: by taz.hyperreal.com (8.6.12/8.6.5) id QAA12122; Mon, 25 Mar 1996 16:12:11 -0800 Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id QAA12116; Mon, 25 Mar 1996 16:12:05 -0800 Received: from zyzzyva.com (randy@localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.4/8.6.11) with ESMTP id SAA18842 for ; Mon, 25 Mar 1996 18:11:32 -0600 (CST) Message-Id: <199603260011.SAA18842@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: Obscure MTU problem In-reply-to: ben's message of Mon, 25 Mar 1996 23:30:53 +0000. <9603252330.aa02562@gonzo.ben.algroup.co.uk> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Mar 1996 18:11:32 -0600 From: Randy Terbush Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > Hi, > > I've just been investigating a problem with our new Apache based > webserver where people using dialups with _some_ ISPs were having extreme > difficulty with our site (intermittently). The symptom at their end was that > they got connected but then hang indefinitely waiting for the data. At our end > we see connections for the data sitting at FIN_WAIT_1 with lots of stuff in > the send queue. > > I seem to have solved this problem by setting the MTU to 512 (default 1500). > SCO 5 is uses Path MTU Discovery (a lot of implementations use MTU=512 for all > nonlocal nets) which is probably the cause of the problem. We don't have any > such problem with a SCO 3 box and an SGI on the same net. > > Any thoughts, anyone? Are these clients MacTCP clients by chance? I understand that Path Discovery on this TCP stack sucks.