From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: option to disable /proc/net/nf_conntrack procfs [was Re: netfilter patches for 3.0.0-rc1]
Date: Fri, 03 Jun 2011 11:50:53 +0200 [thread overview]
Message-ID: <4DE8AE7D.8060609@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1106031052210.32042@frira.zrqbmnf.qr>
On 03/06/11 10:53, Jan Engelhardt wrote:
> netfilter: provide config option to disable ancient procfs parts
>
> Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
> ---
> net/netfilter/Kconfig | 10 ++++++++++
> net/netfilter/nf_conntrack_expect.c | 12 ++++++------
> net/netfilter/nf_conntrack_standalone.c | 4 ++--
> 3 files changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
> index 32bff6d..e4b1076 100644
> --- a/net/netfilter/Kconfig
> +++ b/net/netfilter/Kconfig
> @@ -75,6 +75,16 @@ config NF_CONNTRACK_ZONES
>
> If unsure, say `N'.
>
> +config NF_CONNTRACK_PROCFS
> + bool "Supply CT list in procfs (OBSOLETE)"
> + default y
> + depends on PROC_FS
> + ---help---
> + This option enables for the list of known conntrack entries
> + to be shown in procfs under net/netfilter/nf_conntrack. This
> + is considered obsolete in favor of using the conntrack(8)
> + tool which uses Netlink.
> +
This still misses /proc/net/ip_conntrack which would be available. See
nf_conntrack_l3proto_ipv4_compat.c
next prev parent reply other threads:[~2011-06-03 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 13:47 netfilter patches for 3.0.0-rc1 Pablo Neira Ayuso
2011-06-03 8:53 ` Jan Engelhardt
2011-06-03 9:50 ` Pablo Neira Ayuso [this message]
2011-06-03 14:06 ` option to disable /proc/net/nf_conntrack procfs [was Re: netfilter patches for 3.0.0-rc1] Jan Engelhardt
2011-06-05 23:07 ` Pablo Neira Ayuso
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=4DE8AE7D.8060609@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--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).