From owner-freebsd-questions@FreeBSD.ORG Thu Feb 16 00:33:29 2006 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CEDE16A422 for ; Thu, 16 Feb 2006 00:33:29 +0000 (GMT) (envelope-from danial_thom@yahoo.com) Received: from web33307.mail.mud.yahoo.com (web33307.mail.mud.yahoo.com [68.142.206.122]) by mx1.FreeBSD.org (Postfix) with SMTP id 7264643D48 for ; Thu, 16 Feb 2006 00:33:28 +0000 (GMT) (envelope-from danial_thom@yahoo.com) Received: (qmail 84266 invoked by uid 60001); 16 Feb 2006 00:33:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=k+r3ksQ10NnpzqQhWzG1vH35kZtcn8YoBW9iO5XHhd4lohusB7ff3n+7sqg/Nmuiv9jUQ+qNSk0PYTy2rV0r/bf26H8YldiuoYR69KUFuYE9ko3bSweqCPhNuAVm1o3xSWq0rA4v3odgmT6Zv7LU+K1MqbM6mKnF2laacQD1yxE= ; Message-ID: <20060216003327.84264.qmail@web33307.mail.mud.yahoo.com> Received: from [207.252.75.232] by web33307.mail.mud.yahoo.com via HTTP; Wed, 15 Feb 2006 16:33:27 PST Date: Wed, 15 Feb 2006 16:33:27 -0800 (PST) From: Danial Thom To: brent , freebsd-questions@FreeBSD.org In-Reply-To: <200602160011.k1G0B04O049104@mickey.jensenet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: ethernet Interface haywire ??? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: danial_thom@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2006 00:33:29 -0000 I've seen it happen when the ethernet device gets a bus error and throws it into some strange state. I've seen it mostly with on-board intel devices (fxp), but thats what we use mostly so it may not be part specific. DT --- brent wrote: > Has anyone run into this scenario where a BSD > Box (RELENG_5_4) takes down > the whole subnet for only FreeBSD boxes. > Here’s the scenario: One of my > web servers goes into a crazy state which kills > all traffic on the network > for only FreeBSD boxes. Linux boxes can talk > to other linux boxes, but > FreeBSD boxes are dead. You can ping a FreeBSD > box (from linux) but services > such as SSH go half-way and never completely > connect. Other services such as > http don’t work either. Rebooting that > offending box fixes the problem. > I’ve seen this once it a great moon; however, > it recently happened two > days in a row. Any suggestions would be > appreciated. I have other > RELENG_5_4 and RELENG_6_0 boxes that don’t > seem to be the culprit, as well > as an identical hardware box running > RELENG_6_0. Thanks. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com