Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Andrew J. Meader" <ameader@corp.lcom.net>
To: netfilter@lists.netfilter.org
Cc: ebtables-user@lists.sourceforge.net
Subject: OUI Filtering
Date: Tue, 31 Aug 2004 16:22:55 -0500	[thread overview]
Message-ID: <4134EC2F.8030400@corp.lcom.net> (raw)

Hi Lists,

I'm sending this to both the IPTables and EBTables lists for simplicity.

Does anyone have experience doing MAC address OUI filtering? I am going 
to have a network with mixed broadcast domains - I can not fix this 
because of vendor issues (really, I can't fix this.) There will be one 
place where different ethernets will physically and logically touch, 
they must. I would like to use ebtables to redirect dhcp broadcasts 
based on OUI, one group of devices will have known OUI's. Else, I would 
like to be able to drop dhcp broadcasts based on OUI at the machine that 
doesn't care.

I've done OUI filtering with DHCPd but don't know if it will redirect 
(gut says no.)

Thanks.

Andy



                 reply	other threads:[~2004-08-31 21:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4134EC2F.8030400@corp.lcom.net \
    --to=ameader@corp.lcom.net \
    --cc=ebtables-user@lists.sourceforge.net \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox