From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: IP and MAC Address check
Date: Wed, 5 Oct 2005 01:23:51 -0500 [thread overview]
Message-ID: <200510050123.52028.rob0@gmx.co.uk> (raw)
In-Reply-To: <00cb01c5c970$b6eb9620$580110ac@HO.lippogeneral.com>
On Wednesday 2005-October-05 00:50, Winanjaya - PBXSoftwares wrote:
> > My only comment is that some older systems might not have -m
> > iprange. But no worries, it's not far outside 2 CIDR ranges:
> > 172.16.2.240/29 and 172.16.2.248/30.
> >
> > Ah, one other comment: this might be better structured using a
> > user-defined chain.
(Hold that thought ...)
> so you meant I can use below:
>
> # Range 241 to 246
172.16.2.240/29 is actually 240 through 247.
> -A RH-Lokkit-0-50-INPUT -m mac -s 172.16.2.240/29 ! --mac-source
> 00:12:95:6d:0a:3e -j DROP
> -A RH-Lokkit-0-50-INPUT -m mac -s 172.16.2.240/29 ! --mac-source
> 00:12:95:15:61:14 -j DROP
> -A RH-Lokkit-0-50-INPUT -m mac -s 172.16.2.240/29 ! --mac-source
> 00:12:95:15:62:29 -j DROP
> -A RH-Lokkit-0-50-INPUT -m mac -s 172.16.2.240/29 ! --mac-source
> 00:12:95:15:63:ba -j DROP
RH-Lokkit-0-50? Yuck!!
Okay, trying to regain composure ... :)
Think about this. Look at the first rule:
> -A RH-Lokkit-0-50-INPUT -m mac -s 172.16.2.240/29 ! --mac-source
> 00:12:95:6d:0a:3e -j DROP
If the source IP is in 172.16.2.240/29 and the MAC address is *not*
00:12:95:6d:0a:3e, drop the packet. Your second and subsequent MAC
rules will never be used, because those packets are already dropped.
That's why I'd use another chain for this. Put an ACCEPT rule in the
calling chain after the jump to your new chain. Use -j RETURN rules for
your permitted MAC addresses, and a -j DROP rule at the end of your new
chain.
I hope you do understand about MAC filtering: it only works when your
packets originated on the same physical segment. Anything from outside
your physical segment will come to you with the MAC address of your
upstream router.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-10-05 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 4:24 IP and MAC Address check Winanjaya - PBXSoftwares
2005-10-05 4:58 ` Marcos S. Trazzini
2005-10-05 5:19 ` Winanjaya - PBXSoftwares
2005-10-05 5:23 ` Ruben Cardenal
2005-10-05 5:27 ` hareram
2005-10-05 5:29 ` /dev/rob0
2005-10-05 5:50 ` Winanjaya - PBXSoftwares
2005-10-05 6:23 ` /dev/rob0 [this message]
2005-10-05 6:44 ` Winanjaya - PBXSoftwares
2005-10-05 7:13 ` Rob Sterenborg
2005-10-05 7:52 ` Winanjaya - PBXSoftwares
2005-10-05 8:11 ` Rob Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 5:31 Winanjaya - PBXSoftwares
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=200510050123.52028.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.