From: Chris Brenton <cbrenton@chrisbrenton.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: iptables mailing list <netfilter@lists.netfilter.org>
Subject: Re: efficient source address filtering and logging?
Date: 28 Oct 2003 11:26:10 -0500 [thread overview]
Message-ID: <1067358369.1700.11.camel@valhalla> (raw)
In-Reply-To: <Pine.LNX.4.44.0310280949080.22878-100000@localhost.localdomain>
On Tue, 2003-10-28 at 09:59, Robert P. J. Day wrote:
> i'd like to find a short, efficient way to filter incoming packets with
> bogus source addresses, but i don't see an elegant way of doing it.
Here is what I do in my script to specify my rules:
while read SPOOFED ; do
iptables -A FORWARD -s $SPOOFED -j LOG --log-prefix " SPOOFING "
iptables -A FORWARD -s $SPOOFED -j DROP
done < spoofed_ips.txt
Now you just create a text file called 'spoofed_ips.txt' and add all the
IPs you want to filter, one per line. Use CIDR format to specify
subnets. So your file may look like this:
10.0.0.0/8
192.168.0.0/16
127.0.0.0/8
The only thing you can't specify this way is your internal address space
because the above rules does not tie things to a specific interface
(like external). The reason I do that is so I can catch internal
spoofing as well. Just do a separate spoofing rule for your internal
address space and life will be cool.
This also works well for blocking spammers, known hostile IPs,
countries, etc.
HTH,
C
next prev parent reply other threads:[~2003-10-28 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 14:59 efficient source address filtering and logging? Robert P. J. Day
2003-10-28 15:26 ` James Pattie
2003-10-28 15:32 ` Robert P. J. Day
2003-10-28 15:30 ` Alistair Tonner
2003-10-28 15:33 ` Robert P. J. Day
2003-10-28 16:26 ` Chris Brenton [this message]
2003-11-02 10:29 ` Re[2]: " Peteris Krumins
2003-11-02 11:45 ` Chris Brenton
2003-11-02 13:35 ` Alistair Tonner
2003-11-02 13:48 ` Alistair Tonner
2003-11-04 3:55 ` Tarek W.
[not found] <20031028165927.11207.15406.Mailman@netfilter-sponsored-by.noris.net>
2003-10-28 17:25 ` Earl A.Killian
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=1067358369.1700.11.camel@valhalla \
--to=cbrenton@chrisbrenton.org \
--cc=netfilter@lists.netfilter.org \
--cc=rpjday@mindspring.com \
/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