From owner-freebsd-current Sun Jan 31 02:21:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06857 for freebsd-current-outgoing; Sun, 31 Jan 1999 02:21:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06840; Sun, 31 Jan 1999 02:21:43 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id LAA20746; Sun, 31 Jan 1999 11:21:39 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.2/8.6.9) id KAA00926; Sat, 30 Jan 1999 10:49:58 +0100 (CET) Date: Sat, 30 Jan 1999 10:49:57 +0100 From: Stefan Esser To: Christopher Masto Cc: hardware@FreeBSD.ORG, current@FreeBSD.ORG, Stefan Esser Subject: Re: Network/ARP problem? Maybe pn driver? Message-ID: <19990130104957.B660@dialup124.mi.uni-koeln.de> Reply-To: se@FreeBSD.ORG Mail-Followup-To: Christopher Masto , hardware@FreeBSD.ORG, current@FreeBSD.ORG References: <19990129173922.A29551@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990129173922.A29551@netmonger.net>; from Christopher Masto on Fri, Jan 29, 1999 at 05:39:22PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yust a wild guess: You could have blocked reception of ARP requests / ARP replies in your IPFW rules on one of the systems involved. Just try again with a completely open configuration (a pass all as rule 1 should work). That would explain that other systems can learn the ARP address as soon as they have received IP packets, but they can't get at the ARP address by querying for it ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message