From owner-freebsd-current  Fri Jan 29 14:52:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA25603
          for freebsd-current-outgoing; Fri, 29 Jan 1999 14:52:21 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA25598;
          Fri, 29 Jan 1999 14:52:19 -0800 (PST)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53867(1)>; Fri, 29 Jan 1999 14:52:15 PST
Received: by crevenia.parc.xerox.com id <177534>; Fri, 29 Jan 1999 14:52:13 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: chris@netmonger.net, hardware@FreeBSD.ORG
Subject: Re:  Network/ARP problem?  Maybe pn driver?
Cc: current@FreeBSD.ORG
Message-Id: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>
Date: Fri, 29 Jan 1999 14:52:07 PST
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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).

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message