From owner-freebsd-hackers Mon Aug 28 21: 7:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id F049D37B424 for ; Mon, 28 Aug 2000 21:07:47 -0700 (PDT) Received: (qmail 51754 invoked from network); 29 Aug 2000 04:07:44 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 29 Aug 2000 04:07:44 -0000 Date: Mon, 28 Aug 2000 21:07:32 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Bill Fumerola Cc: Simon , "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: <20000828233106.T33771@jade.chc-chimes.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can appreciate the sarcasm... However, given today's generally IP-only connected networks, ipfw does not seem to be a necessarily bad place to do this kind of filtering... I only mention it because dummynet could be useful bandwidth limiting to MAC addresses as well. And it never hurts to ask to see if somebody else has hacked it in, even if the command name isn't exactly descriptive... On Mon, 28 Aug 2000, Bill Fumerola wrote: > On Mon, Aug 28, 2000 at 07:02:03PM -0700, Jaye Mathisen wrote: > > > > Just exactly what I said in the Subject. I want to filter on the ethernet > > MAC address. > > I guess the "ip" in "ipfw" just wasn't obvious enough that it is an IP firewall > tool. You're one layer too low. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message