From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Sudheer Divakaran' <sudheer@svw.com>,
'Netfilter mailing list' <netfilter@lists.netfilter.org>
Subject: RE: A simple question
Date: Wed, 18 Aug 2004 21:18:54 -0700 [thread overview]
Message-ID: <SERVER7QYx3G5aYY61L00000074@server7.bandwidthco.com> (raw)
In-Reply-To: <41241244.40804@svw.com>
In almost all IP Tables articles I've found that the default policy of all
tables (INPUT,OUTPUT,FORWARD) set to DROP. I can understand it as far as
INPUT and FORWARD tables are concerned, but I do not understand why should
we set the default policy of OUTPUT chain to DROP. OUTPUT chain is
responsible for packets originating from the firewall itself.
Whay should we DROP it?
Thanks,
Sudheer
What you say is indeed correct. Most of the articles on the subject do
recommend a default DROP on all three tables. However, I personally do set
my OUTPUT default to ACCEPT, while my FORWARD and INPUT are definitely set
to DROP. As you might expect, it is quite easy to DOS the firewall itself
when OUTPUT is set to DROP. And that is not a real good idea. However,
having said that, close scrutiny must be paid to what you allow out of the
firewall and the necessary rules must be in place.
next prev parent reply other threads:[~2004-08-19 4:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 2:36 A simple question Sudheer Divakaran
2004-08-19 4:18 ` Mark E. Donaldson [this message]
2004-08-19 8:39 ` Torsten Luettgert
2004-08-19 4:52 ` Dhananjoy Chowdhury
2004-08-19 15:46 ` Erick Sanz
-- strict thread matches above, loose matches on Subject: below --
2005-08-10 0:11 A Simple Question Robb Bossley
2005-08-10 19:58 ` /dev/rob0
2005-08-11 5:54 ` Jan Engelhardt
2005-08-12 5:27 ` Grant Taylor
2004-08-19 17:58 A simple question Hudson Delbert J Contr 61 CS/SCBN
2004-08-19 17:47 Daniel Chemko
2004-08-19 17:14 Daniel Chemko
2004-08-19 17:31 ` Nick Drage
2004-08-19 15:15 Hudson Delbert J Contr 61 CS/SCBN
2004-08-19 11:04 Jason Opperisano
2004-04-06 2:25 Gianni Pucciani
2004-04-05 22:40 ` Antony Stone
2004-04-06 13:26 ` Gianni Pucciani
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=SERVER7QYx3G5aYY61L00000074@server7.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=netfilter@lists.netfilter.org \
--cc=sudheer@svw.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