[PATCH][v2] Netfilter Kconfig: Expose IPv4/6 connection
tracking options by selecting NF_CONNTRACK_ENABLED
yasuyuki.kozakai at toshiba.co.jp
Thu Jul 26 03:18:22 CEST 2007
From: Patrick McHardy <kaber at trash.net>
Date: Thu, 26 Jul 2007 02:46:05 +0200
> [Removed a few CCs]
> Al Boldi wrote:
> > Make NF_CONNTRACK_IPV4 and NF_CONNTRACK_IPV6 select NF_CONNTRACK_ENABLED.
> One thought that occured to me after the last of many false bugreports
> that were actually caused by failure to configure the new options
> properly. Most people know they want NF_CONNTRACK (and its selected by
> default with old configs), what they're missing is that they now also
> need to select IPv4 connection tracking. So what would really make sense
> is to make NF_CONNTRACK_IPV4 default to "m" (and really *everyone*
> using conntrack wants this). But with your proposed change this would
> default to selecting NF_CONNTRACK by default, which I'm not so sure
> is a good idea. So I'm leaning towards just using "m" as default for
> IPv4 conntrack to save people trouble and myself some bugreports, but
> I also like your simplification ...
> Maybe we can do something to have the NF_CONNTRACK_ENABLED option select
> NF_CONNTRACK_IPV4 (which really is what we actually want) and combine
> that with automatic selection of NF_CONNTRACK? I believe the only case
> with negative impact would be people that currently use only IPv6
> connection tracking, which is most likely nobody.
I agree. I've not heard trouble with NF_CONNTRACK_IPV6. I think that is
because it is purely new feature.
BTW, it's too late to restore IP_NF_CONNTRACK in stable and current tree
for a while ?
-- Yasuyuki Kozakai
More information about the netfilter-devel