netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: CONFIG_NETFILTER_ADVANCED
Date: Sun, 18 Nov 2007 14:21:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711181407270.17843@blackhole.kfki.hu> (raw)
In-Reply-To: <473FA140.7080708@trash.net>

Hi Patrick,

On Sun, 18 Nov 2007, Patrick McHardy wrote:

> For people who want to compile-test them all (like me), we
> still can have a CONFIG_NETFILTER_ALL option hidden under
> CONFIG_NETFILTER_ADVANCED for simplicity, but that is a
> different topic.

I think the other way around would be better:

CONFIG_NETFILTER		enable everyting
CONFIG_NETFILTER_WITHOUT_NAT	everything except NAT
CONFIG_NETFILTER_ADVANCED	select modules manually

This is more or less the most usual cases: typically almost everyone wants 
NAT and the wide range of matches and targets. Some places don't use NAT. 
And if someone wants to exclude modules or disable settings like 
conntrack flow accounting, in advanced mode it'd be possible to do so.

Best regards,
Jozsef
-
E-mail  : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
          H-1525 Budapest 114, POB. 49, Hungary

  parent reply	other threads:[~2007-11-18 13:21 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                 ` CONFIG_NETFILTER_ADVANCED Patrick McHardy
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                           ` Jozsef Kadlecsik [this message]
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=Pine.LNX.4.64.0711181407270.17843@blackhole.kfki.hu \
    --to=kadlec@blackhole.kfki.hu \
    --cc=kaber@trash.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).