From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: David Miller <davem@davemloft.net>,
jengelh@computergmbh.de, netfilter-devel@vger.kernel.org
Subject: Re: CONFIG_NETFILTER_ADVANCED
Date: Fri, 16 Nov 2007 16:47:24 +0100 [thread overview]
Message-ID: <473DBB8C.9020709@trash.net> (raw)
In-Reply-To: <20071116153541.GA25986@linuxace.com>
Phil Oester wrote:
> On Fri, Nov 16, 2007 at 01:49:45PM +0100, Patrick McHardy wrote:
>> What I have in mind is roughly:
>>
>> IPv4/IPv6 conntrack
>> NAT
>> ip_tables/ip6_tables
>> tables: filter, nat
>> matches: tcpudp, state, limit, hashlimit, policy
>> targets: LOG, NFLOG, TCPMSS, REJECT, MASQUERADE
>>
>> That should be enough for a simple firewall script. I'm not sure
>> whether we should also select helpers though. Maybe the common
>> ones, like ftp, irc and sip?
>
> I'd vote for at least FTP here...most users will use it at
> some point (or if they don't, wonder why FTP is broken).
I agree. It would be useful if some users of a distribution that
includes a firewall script could check which modules it requires.
next prev parent reply other threads:[~2007-11-16 15:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 0:01 CONFIG_NETFILTER_ADVANCED David Miller
2007-11-16 0:06 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-16 0:41 ` CONFIG_NETFILTER_ADVANCED Jan Engelhardt
2007-11-16 10:10 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-16 10:12 ` CONFIG_NETFILTER_ADVANCED David Miller
2007-11-16 12:19 ` CONFIG_NETFILTER_ADVANCED Jan Engelhardt
2007-11-16 12:44 ` CONFIG_NETFILTER_ADVANCED David Miller
2007-11-16 12:49 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-16 15:35 ` CONFIG_NETFILTER_ADVANCED Phil Oester
2007-11-16 15:47 ` Patrick McHardy [this message]
2007-11-16 23:29 ` CONFIG_NETFILTER_ADVANCED Amos Jeffries
2007-11-17 0:13 ` CONFIG_NETFILTER_ADVANCED Tom Eastep
2007-11-17 16:08 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-17 21:19 ` CONFIG_NETFILTER_ADVANCED Jan Engelhardt
2007-11-18 2:19 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-18 9:35 ` CONFIG_NETFILTER_ADVANCED Jan Engelhardt
2007-11-18 13:21 ` CONFIG_NETFILTER_ADVANCED Jozsef Kadlecsik
2007-11-18 21:40 ` CONFIG_NETFILTER_ADVANCED David Miller
2007-11-27 16:34 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
2007-11-17 0:19 ` CONFIG_NETFILTER_ADVANCED David Miller
2007-11-17 8:48 ` CONFIG_NETFILTER_ADVANCED Benny Amorsen
2007-11-17 15:29 ` CONFIG_NETFILTER_ADVANCED Pascal Hambourg
2007-11-17 16:14 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2007-11-18 6:05 CONFIG_NETFILTER_ADVANCED Al Boldi
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=473DBB8C.9020709@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=jengelh@computergmbh.de \
--cc=kernel@linuxace.com \
--cc=netfilter-devel@vger.kernel.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.