From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@inl.fr>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Dump mark even if event is a DESTROY event
Date: Wed, 21 Feb 2007 13:51:30 +0100 [thread overview]
Message-ID: <45DC4052.2010305@netfilter.org> (raw)
In-Reply-To: <1171964721.26768.4.camel@localhost.localdomain>
Hi Eric,
Eric Leblond wrote:
> Mark is scarcely dump by nfnetlink_conntrack event handler. As it can be
> used to test that a connection is part of a given subset, I think it
> should be almost always dumped.
I don't see why you may need the mark in the destroy message. You can
keep a cache in userspace with the connections that belong to a certain
subset and their marks, then if the mark changes, move such connection
the a different subset. It doesn't make sense to me the idea of
including the mark in the destroy message since such mark didn't change
with regards to the previous event delivered.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2007-02-21 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 9:45 [PATCH] Dump mark even if event is a DESTROY event Eric Leblond
2007-02-21 12:51 ` Pablo Neira Ayuso [this message]
2007-02-21 13:13 ` Eric Leblond
2007-02-23 10:45 ` Amin Azez
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=45DC4052.2010305@netfilter.org \
--to=pablo@netfilter.org \
--cc=eric@inl.fr \
--cc=netfilter-devel@lists.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 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.