From owner-freebsd-questions@FreeBSD.ORG Sun Nov 6 13:19:55 2005 Return-Path: X-Original-To: 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 C62AB16A41F for ; Sun, 6 Nov 2005 13:19:55 +0000 (GMT) (envelope-from david.fleck@mchsi.com) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685C443D45 for ; Sun, 6 Nov 2005 13:19:55 +0000 (GMT) (envelope-from david.fleck@mchsi.com) Received: from grond (12-216-7-29.client.mchsi.com[12.216.7.29]) by sccmmhc91.asp.att.net (sccmmhc91) with SMTP id <20051106131953m9100du96ke>; Sun, 6 Nov 2005 13:19:54 +0000 Date: Sun, 6 Nov 2005 07:19:53 -0600 (CST) From: David Fleck Sender: dcf@grond.sourballs.org To: Steve Bertrand In-Reply-To: <200511051530.jA5FU5qs000530@grond.sourballs.org> Message-ID: <20051106071527.B278@grond.sourballs.org> References: <200511051530.jA5FU5qs000530@grond.sourballs.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: 'FreeBSD Questions' Subject: RE: getting an old NIC to work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Nov 2005 13:19:55 -0000 On Sat, 5 Nov 2005, Steve Bertrand wrote: > It appears as though everything is in order. The routes are in place, > IP/SN is all correct etc. > > You are going to have to take a step down now to the lower layers of the > network stack. > > Perform this command while plugged into the network and let it run a > while: > > # tcpdump -n -i pcn0 > > What this will do is see if the nic can see traffic coming from other > machines. Throw some pings at it from another box, and even if the other > box doesn't get a reply, tcpdump will tell you if the nic can at least > see the incoming traffic. Also, run tcpdump on another box, and repeat > the process, but ping from the box with the 'bad' nic in it. Perhaps it > can send traffic, but just not receive. Doing this both ways will > indicate either way and may give you a clue. No indication of activity either way - 'tcpdump' on the affected machine sees no packets from elsewhere, 'tcpdump' on a working machine sees tons of packets, but none from this machine. > Further that, even farther down, try a different cable and switch port > (one at a time). I know that may seem silly, but weirder things have > happened. Yes, I know... tried swapping cables/hub ports, no change. > If all of that fails, due to the fact there is a driver loaded for the > device, and it is taking all of it's parameters ok, I would say slap a > new nic in the box and see if you can rx/tx traffic via it. If you can, > I'd say then there is a problem with the nic itself, and you have > confirmed it logically and completely. Well, that may take a few days, until I scrounge up an extra NIC... but thanks for the assistance. At least I know I was going about the testing the right way. -- David Fleck david.fleck@mchsi.com