Date: Thu, 7 Jan 1999 11:16:52 -0600 From: Nathan Ahlstrom <nrahlstr@winternet.com> To: David Kulp <dkulp@neomorphic.com>, freebsd-questions@FreeBSD.ORG Subject: Re: How to diagnose bad ethernet? Message-ID: <19990107111652.F29582@winternet.com> In-Reply-To: <199901071706.JAA09805@board66.cruzers.com>; from David Kulp on Thu, Jan 07, 1999 at 09:06:05AM -0800 References: <199901071706.JAA09805@board66.cruzers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Kulp <dkulp@neomorphic.com> wrote: > I'm getting log files containing errors like the following. Are there > diagnostic tools for tracing down the problem in the network? For > starters (stupid question) how do I determine which ethernet address > is which IP address (without typing ifconfig or similar on each > console)? And is there stress testing that can be run on the network? Bad cables. Search for "comments on de driver error message?" in the hackers mail archives. Good Luck. Nathan -- Nathan Ahlstrom nrahlstr@winternet.com Run FreeBSD: http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990107111652.F29582>