From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: IP + MAC filter - doubt
Date: Wed, 04 May 2005 22:43:07 -0500 [thread overview]
Message-ID: <4279964B.90001@riverviewtech.net> (raw)
In-Reply-To: <c76dd6c78318.c78318c76dd6@vsnl.net>
> A FORWARD -i eth1 -o eth0 -s 192.168.0.5 \
> -m mac --mac-source XX:XX:XX:XX:XX:XX -j ACCEPT
>
> First tell me if above rule correct.
Yes, that is one way to do it. The ""other way(s) have to do with ACCEPTing vs redirecting to another chain for additional testing.
> Second I think I need first a rule to
> deny all IPs and MACs. Is that correct ?
Yes you will need a rule (or FORWARD policy) to not forward or DROP packets. I would put this at the end of your FORWARD chain (or at least the section that does your MAC to IP pairing) after you have decided what MAC IP pairs to allow through. Explicitly allow what you want to get out and then DROP or REJECT the rest of the chaff.
> Howto first deny all IPs and MACs ?
iptables -t filter -A FORWARD -i eth1 -o eth0 -j DROP
> Thanks in advance
No problem.
Grant. . . .
next prev parent reply other threads:[~2005-05-05 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 2:26 IP + MAC filter - doubt varun_saa
2005-05-05 3:43 ` Taylor, Grant [this message]
2005-05-10 8:38 ` Georgi Alexandrov
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=4279964B.90001@riverviewtech.net \
--to=gtaylor@riverviewtech.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