Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Thomas Mader <thezema@gmail.com>,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: libnetfilter_queue and libnetfilter_conntrack API questions
Date: Wed, 09 Apr 2008 17:02:24 +0200	[thread overview]
Message-ID: <47FCDA80.10005@netfilter.org> (raw)
In-Reply-To: <47FCD84A.7030400@trash.net>

Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>> The events do not include the ID, this is how it goes as for now.
>> Actually I'm not a big fun of the ID.
>>
>> @Patrick: I don't remember exactly the reason why we decided to keep the
>> ID there, and if we have decided to do so, it seems inconsistent to me
>> not to include it in the events.
> 
> 
> I agree. I guess the reason why its not sent on events is that it
> was originally only introduced (IIRC, I might be confusing it with
> the ordered list on second thought) for dumps.
> 
> The reason why we kept it at all is that people are already using
> it as unique identifier, we only changed the uniqueness to mean
> "unique at any given point in time", but not over time. I guess
> the logical thing to do would be to also include it in events.
> I know some people are using patches to do this already.

Well, I'm not big fun of reducing the limited bandwidth of netlink but
let's inserted it. I have a couple of patches here for ctnetlink. I can
include one for this.

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2008-04-09 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 14:06 libnetfilter_queue and libnetfilter_conntrack API questions Thomas Mader
2008-04-09 14:46 ` Pablo Neira Ayuso
2008-04-09 14:52   ` Patrick McHardy
2008-04-09 15:02     ` Pablo Neira Ayuso [this message]
2008-04-09 15:07       ` Patrick McHardy
2008-04-09 16:00   ` Thomas Mader

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=47FCDA80.10005@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=thezema@gmail.com \
    /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