All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg <lego12239@yandex.ru>
To: netdev@vger.kernel.org
Subject: Re: CONFIG_NF_CONNTRACK_PROCFS
Date: Sun, 25 Jan 2015 22:44:35 +0300	[thread overview]
Message-ID: <20150125194435.GA12981@localhost> (raw)
In-Reply-To: <20150125112209.GD13167@breakpoint.cc>

On Sun, Jan 25, 2015 at 12:22:09PM +0100, Florian Westphal wrote:
> Oleg <lego12239@yandex.ru> wrote:
> > net/netfilter/nf_conntrack procfs file is marked as obsolete in the recent
> > kernels. What's wrong with it? Or it's simply a new fashion to replace
> > simple file interface with anything else?
> 
> proc has several drawbacks vs. ctnetlink:
>  - not extensible

In the what way?
Sorry, but i think that limitations isn't in proc, but in a human fantasy.

>  - doesn't have ability to query for particular items

What about something like:

exec 3<>nf_conntrack; echo show tcp dport 12345 >&3; cat <&3
HERE_WE_GET_NEEDED_ENTRIES
exec 3<&-

?

>  - no add/delete support

What about simple:

echo add ENTRY > nf_conntrack
echo delete ENTRY > nf_conntrack

?

>  - no event notification (e.g. conntrack -E)

Florian, are you seriosly? What's wrong with simple:

cat nf_conntrack_event

?

Moreover, all things i have wrote save already existent scripts works.

May be i don't understand anything? Please correct me if so.

P.S. netlink is really cool thing, but i think we go in the wrong way.

-- 
Nemanov Oleg

      reply	other threads:[~2015-01-25 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25  5:51 CONFIG_NF_CONNTRACK_PROCFS Oleg
2015-01-25 11:22 ` CONFIG_NF_CONNTRACK_PROCFS Florian Westphal
2015-01-25 19:44   ` Oleg [this message]

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=20150125194435.GA12981@localhost \
    --to=lego12239@yandex.ru \
    --cc=netdev@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.