netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KOVACS Krisztian <hidden@balabit.hu>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: nfnetlink and conntrack extension question
Date: Thu, 08 Dec 2011 10:56:16 +0100	[thread overview]
Message-ID: <4EE089C0.8000902@balabit.hu> (raw)
In-Reply-To: <alpine.LNX.2.01.1112042202420.5627@frira.zrqbmnf.qr>

Hi,

On Sun 04 Dec 2011 10:06:12 PM CET, Jan Engelhardt wrote:
> On Wednesday 2011-11-30 19:22, Pablo Neira Ayuso wrote:
>>> As for 1, you can use genetlink, just as I do for the copy of ipset
>>> in xtables-addons. Being forced to use nfnetlink has been point of
>>> much discussion and ultimately, nobody was able to provide a
>>> technical reason on why nfnetlink is better.

Thanks for the suggestion, guys. We could definitely use genetlink 
instead of nfnetlink for the userspace-kernelspace communication stuff.

However, this still leaves us with the second problem -- registering a 
conntrack extension without recompiling the conntrack module. That one 
is still more or less a show-stopper for us, unless we implement our 
own state table effectively duplicating the features of the conntrack 
hash and do a lookup every time we need policy information. Neither of 
these options is particularly nice.

-- 
KOVACS Krisztian


  reply	other threads:[~2011-12-08  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 15:54 nfnetlink and conntrack extension question KOVACS Krisztian
2011-11-30 17:05 ` Jan Engelhardt
2011-11-30 18:22   ` Pablo Neira Ayuso
2011-12-04 21:06     ` Jan Engelhardt
2011-12-08  9:56       ` KOVACS Krisztian [this message]
2011-11-30 18:09 ` Pablo Neira Ayuso
2011-12-08 10:06   ` KOVACS Krisztian

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=4EE089C0.8000902@balabit.hu \
    --to=hidden@balabit.hu \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).