From owner-freebsd-stable@FreeBSD.ORG Wed Sep 24 13:42:19 2003 Return-Path: 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 1A44916A4B3 for ; Wed, 24 Sep 2003 13:42:19 -0700 (PDT) Received: from dglawrence.com (12-224-163-157.client.attbi.com [12.224.163.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3D3D44025 for ; Wed, 24 Sep 2003 13:42:16 -0700 (PDT) (envelope-from dg@nexus.dglawrence.com) Received: from nexus.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.12.9/8.12.6) with ESMTP id h8OKipEd010361; Wed, 24 Sep 2003 13:44:51 -0700 (PDT) (envelope-from dg@nexus.dglawrence.com) Received: (from dg@localhost) by nexus.dglawrence.com (8.12.9/8.12.3/Submit) id h8OKipR9010360; Wed, 24 Sep 2003 13:44:51 -0700 (PDT) Date: Wed, 24 Sep 2003 13:44:51 -0700 From: "David G. Lawrence" To: Jeff Love Message-ID: <20030924204451.GA10540@nexus.dglawrence.com> References: <6.0.0.22.0.20030924103406.0307c250@209.112.4.2> <20030924151245.GA7400@shellma.zin.lublin.pl> <6.0.0.22.0.20030924111529.05a965d0@209.112.4.2> <20030924153450.GB7648@shellma.zin.lublin.pl> <6.0.0.22.0.20030924114051.06fb5e58@209.112.4.2> <20030924160520.GA7970@shellma.zin.lublin.pl> <6.0.0.22.0.20030924121543.08c1c060@209.112.4.2> <3F71C4E9.8030801@snu.ac.kr> <3F71C6E9.5070903@burghcom.com> <3F71FF90.4050503@burghcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F71FF90.4050503@burghcom.com> cc: freebsd-stable@freebsd.org Subject: Re: "No route to host after certain time" is fxp only? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 20:42:19 -0000 > Is this happening only with fxp (intel) network cards? I run them, and > have only seen this problem detailed regarding fxp cards thus far on > this list. Someone reported the problem with the vr chips as well. It does not appear to have anything to do with the driver. It appears to be caused by the 'arp security fix' that was committed last week. > Any idea if there is a fix forthcoming? It should be backed out immediately, troubleshooted, and recommitted later when it has been debugged - hopefully in time for the 4.9 release. This is another serious bug coming in right before the release which is only going to turn people off of -stable again, precisely at the time when we need the most people using it. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.