From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Netfilter Performance when using MAC filter
Date: Wed, 31 Oct 2007 13:41:44 -0500 [thread overview]
Message-ID: <4728CC68.9000804@riverviewtech.net> (raw)
In-Reply-To: <1193855211.18366.73.camel@grateful.d.umn.edu>
On 10/31/07 13:26, Matt Zagrabelny wrote:
> If so, you can do MAC filtering (performance shouldn't matter as the
> MAC address is in the link header), if not MAC filtering won't buy
> you much, the layer2 address will always be the same.
Agreed.
However this can also be extended to help prevent spoofing in a routed
network. If you know that a given subnet is available via a given
router or routers you can only accept the packet if the source IP is
coming from said router's MAC address. Thus preventing someone else in
a different subnet from spoofing the source IP address. Or for those of
us who like to run basic layer 3 filtering on all routers that would
prevent such spoofed addresses, you can prevent someone from spoofing IP
addresses with in the core network, i.e. backbone LAN trying to claim to
be someone else.
This can and will work fairly well, though you have to be aware that
this is in effect if you ever change MAC addresses of routers.
If you are going to go this route, I'd suggest that you use your own
private OUI MAC addresses on routers. This way you know that you need
to alter the MAC on the routers when you put them in place to support
your security model.
> This is essentially the difference between ARP and IP, or switching
> and routing if you prefer.
*nod*
Or brouting (bridging / routing combination) if you so choose to go there.
Grant. . . .
next prev parent reply other threads:[~2007-10-31 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 16:23 Netfilter Performance when using MAC filter Babu Skeitson
2007-10-31 18:26 ` Matt Zagrabelny
2007-10-31 18:41 ` Grant Taylor [this message]
2007-10-31 19:19 ` Pascal Hambourg
2007-10-31 19:33 ` Matt Zagrabelny
2007-11-01 10:05 ` Pascal Hambourg
2007-11-01 13:17 ` Matt Zagrabelny
2007-11-01 14:55 ` Pascal Hambourg
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=4728CC68.9000804@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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