From owner-freebsd-stable@FreeBSD.ORG Fri Aug 26 13:50:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4B9B16A41F for ; Fri, 26 Aug 2005 13:50:43 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7009943D46 for ; Fri, 26 Aug 2005 13:50:43 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 17246 invoked from network); 26 Aug 2005 13:50:43 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 Aug 2005 13:50:43 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id EDCA847; Fri, 26 Aug 2005 09:50:41 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Bryan Buecking References: <430C3858.4090501@vanten.com> <20050824112228.M82971@govital.net> <430D2527.1040004@vanten.com> From: Lowell Gilbert Date: 26 Aug 2005 09:50:41 -0400 In-Reply-To: <430D2527.1040004@vanten.com> Message-ID: <44mzn424em.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org Subject: Re: CVSup timeout 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: Fri, 26 Aug 2005 13:50:43 -0000 Bryan Buecking writes: > Chris Demers wrote: > > I have run into this myself in my own home network, what I have > > found that fixed it is I just adjusted the MTU on all my stations > > with problems to the size of the pppoe packet size. From the error > > try changing it to in your case 1454 and see if the error goes away. > > > Thanks, that did it. I tried adjusting my MTU before, but did not > consider the MTU of the FW; which happens to be set to 1450. So > setting the MTU of problematic machine to 1450, and not 1454, fixed my > issues. > > I guess the only other point worth mentioning is the fact that with > fbsd 4.11 works fine with an MTU of 1500. I'm not sure, but could > this have something to do with DF bit not being set correctly? Possible, but it may be more likely that a firewall is improperly dropping ICMP messages to break MTU discovery.