From owner-freebsd-hardware Fri Jan 29 15:06:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27351 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:06:19 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27330; Fri, 29 Jan 1999 15:06:15 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA04552; Fri, 29 Jan 1999 18:06:12 -0500 (EST) Message-ID: <19990129180612.C3237@netmonger.net> Date: Fri, 29 Jan 1999 18:06:12 -0500 From: Christopher Masto To: Bill Fenner , hardware@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <99Jan29.145213pst.177534@crevenia.parc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>; from Bill Fenner on Fri, Jan 29, 1999 at 02:52:07PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote: > Can you run a "tcpdump arp" on the machine that is having the problem, > as well? This could help to determine if it's a driver problem (e.g. > if the replies don't show up) or an ARP problem (e.g. if the replies > do show up but arp doesn't use them). Good idea. Hmm. Running tcpdump seems to make the problem go away. The ARP replies show up immediately appear in the table. Clue. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message