From owner-freebsd-questions Thu Jan 7 09:29:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11071 for freebsd-questions-outgoing; Thu, 7 Jan 1999 09:29:33 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from iworks.interworks.org (iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11063 for ; Thu, 7 Jan 1999 09:29:30 -0800 (PST) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id LAA04187; Thu, 7 Jan 1999 11:29:27 -0600 (CST) Date: Thu, 7 Jan 1999 11:29:27 -0600 (CST) From: "Daniel M. Eischen" Message-Id: <199901071729.LAA04187@iworks.interworks.org> To: dkulp@neomorphic.com Subject: Re: How to diagnose bad ethernet? Cc: freebsd-questions@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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? You probably have a cabling problem. Find the machines with ethernet addresses 00:c0:7b:4e:a2:6d and 00:40:10:07:1c:d9 and replace their cables with known good cables. Use arp -a to find the IP addresses from ethernet addresses. You can also search the -hackers mail archives for a very recent discussion ov the above problem. Search for "comments on de driver error message". Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message