From: "Philippe Anctil" <z77y16@hotmail.com>
To: netfilter@lists.netfilter.org
Subject: safe default chain policies
Date: Thu, 01 Apr 2004 23:58:08 -0500 [thread overview]
Message-ID: <BAY16-F59EdJ7BzKkc100034639@hotmail.com> (raw)
Hello list,
I've had quite a bit of trouble setting up nat rules on my iptables home
network firewall. Machines behind my firewall box couldn't host games, use
bittorrent efficiently, that type of thing. Not that nothing works. I've
been surfing, playing games and ftp'ing happily for a while. My problems
were nat-specific.
I have known for a while my problems were related to my default chain
policies. I never wanted to compromise security, so I set all of input and
nat chains to DROP. I left the mangle to accept (never took time to
understand this table). Is this excessive security? I find such a firewall
quite hard to maintain because you need to know exactly how chains are
traversed.
I am thinking to set all chains to ACCEPT except the INPUT chain. Is this
minimalist security? This is one chain I think I should not be open.
Where to draw the line for a home network?
Thanks for sharing your thoughts!
_________________________________________________________________
MSN Messenger : discutez en direct avec vos amis !
http://messenger.fr.msn.ca/
next reply other threads:[~2004-04-02 4:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 4:58 Philippe Anctil [this message]
2004-04-02 7:42 ` safe default chain policies Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 15:21 Philippe Anctil
2004-04-02 15:36 ` Antony Stone
2004-04-02 15:44 ` Antony Stone
2004-04-02 19:02 Philippe Anctil
2004-04-02 19:23 ` Antony Stone
2004-04-02 19:12 Philippe Anctil
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=BAY16-F59EdJ7BzKkc100034639@hotmail.com \
--to=z77y16@hotmail.com \
--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