From: Ted Kaczmarek <tedkaz@optonline.net>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: Lista de Mail netfilter <netfilter@lists.netfilter.org>
Subject: Re: IP Spoofing
Date: Fri, 07 Nov 2003 07:26:50 -0500 [thread overview]
Message-ID: <1068208010.29753.10.camel@tarkus> (raw)
In-Reply-To: <200311052039.hA5KdYr13351@agate.rockstone.co.uk>
I would add an input established on that as well, makes it easier to do
upgrades.
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
I wish everyone did implicit DROP's, it would make the web a safer
place.
:-)
Ted
On Wed, 2003-11-05 at 15:39, Antony Stone wrote:
> On Wednesday 05 November 2003 8:19 pm, Leandro Takashi Hirano wrote:
>
> > Thanks Antony...
> >
> > Do you have a script or something where I can find protection rules?
>
> You tell us what protection you want and we can suggest some rules to do it.
>
> There's no single "magic ruleset" for netfilter / iptables which "protects
> your network", otherwise every distribution would include it as standard.
>
> It depends what you want to do.
>
> A good starting point is:
>
> iptables -P INPUT DROP
> iptables -P OUTPUT DROP
> iptables -P FORWARD DROP
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i $intIF -o $extIF -j ACCEPT
>
> That will allow nothing in or out of the firewall machine itself, and will
> allow all access from your internal network to the Internet, blocking
> everything except reply packets from the Internet to your network.
>
> I do not recommend that you simply implement the above rules before you
> understand what they are designed to do.
>
> Check Oskar Andreasson's excellent tutorial for more information about this
> sort of configuration, or any of the other documentation at
> http://www.netfilter.org
>
> Antony.
next prev parent reply other threads:[~2003-11-07 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 19:31 IP Spoofing Leandro Takashi Hirano
2003-11-05 19:51 ` Antony Stone
2003-11-05 20:08 ` David C. Hart
2003-11-05 20:10 ` Antony Stone
2003-11-05 20:26 ` Jeffrey Laramie
2003-11-05 20:57 ` David C. Hart
2003-11-05 21:22 ` Jeffrey Laramie
2003-11-05 20:19 ` Leandro Takashi Hirano
2003-11-05 20:39 ` Antony Stone
2003-11-07 12:26 ` Ted Kaczmarek [this message]
2003-11-07 12:32 ` Antony Stone
2003-11-07 13:34 ` David C. Hart
2003-11-07 13:56 ` Antony Stone
2003-11-07 14:04 ` David C. Hart
2003-11-08 18:06 ` Ted Kaczmarek
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 20:53 bmcdowell
2003-04-10 20:39 IP spoofing Daniel Chemko
2003-04-10 20:26 Farshad
2003-04-10 21:10 ` Peteris Krumins
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=1068208010.29753.10.camel@tarkus \
--to=tedkaz@optonline.net \
--cc=Antony@Soft-Solutions.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.