From owner-freebsd-hardware Mon Feb 1 00:19:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11096 for freebsd-hardware-outgoing; Mon, 1 Feb 1999 00:19:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11080; Mon, 1 Feb 1999 00:19:06 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA19979; Mon, 1 Feb 1999 07:06:56 +0100 From: Luigi Rizzo Message-Id: <199902010606.HAA19979@labinfo.iet.unipi.it> Subject: Re: Network/ARP problem? Maybe pn driver? To: archie@whistle.com (Archie Cobbs) Date: Mon, 1 Feb 1999 07:06:56 +0100 (MET) Cc: se@FreeBSD.ORG, chris@netmonger.net, hardware@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199902010651.WAA25847@bubba.whistle.com> from "Archie Cobbs" at Jan 31, 99 10:51:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Stefan Esser writes: > > 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 > > FYI- > There's no way to block ARP packets with ipfw... it only > deals with IP packets. er... if you use bridging and enable ipfw on bridged packets (net.link.ether.bridge_ipfw=1) then you can block non-ip packets if you don't use an open firewall. I don't think the original poster is in this situation that's why i did not spoke before. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message