From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Jan Engelhardt <jengelh@medozas.de>
Cc: ext Pablo Neira Ayuso <pablo@netfilter.org>,
Changli Gao <xiaosuo@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] netfilter: xtables: userspace notification target
Date: Tue, 13 Jul 2010 16:24:33 +0300 [thread overview]
Message-ID: <1279027474.12673.61.camel@chilepepper> (raw)
In-Reply-To: <alpine.LSU.2.01.1007131349120.778@obet.zrqbmnf.qr>
On Tue, 2010-07-13 at 13:49 +0200, ext Jan Engelhardt wrote:
> On Tuesday 2010-07-13 12:23, Luciano Coelho wrote:
> >>
> >> Indeed, this looks to me like something that you can do with NFLOG and
> >> some combination of matches.
> >
> >Is it possible to have the NFLOG send only one notification to the
> >userspace? In the example above, once the quota exceeds, the userspace
> >will be notified of every packet arriving, won't it? That would cause
> >unnecessary processing in the userspace.
> >
> >The userspace could remove the rule when it gets the first notification
> >and only add it again when it needs to get the information again (as a
> >"toggle" functionality), but I think that would take too long and there
> >would be several packets going through before the rule could be removed.
>
> With xt_condition that should not be a problem
> (-A INPUT -m condition --name ruleXYZ -j NFLOG..)
> This is settable through procfs.
Right. I didn't know about the condition match, because I can't see it
either on net-next-2.6 nor on nf-next-2.6. I found your patch in the
netfilter-devel archives, though. Any idea when it will be applied?
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-07-13 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 0:11 [PATCH] netfilter: xtables: userspace notification target Samuel Ortiz
2010-07-13 5:56 ` Jan Engelhardt
2010-07-13 13:19 ` Samuel Ortiz
2010-07-13 6:18 ` Changli Gao
2010-07-13 8:50 ` Pablo Neira Ayuso
2010-07-13 10:23 ` Luciano Coelho
2010-07-13 11:49 ` Jan Engelhardt
2010-07-13 13:24 ` Luciano Coelho [this message]
2010-07-13 16:38 ` Pablo Neira Ayuso
2010-07-14 11:48 ` Patrick McHardy
2010-07-14 12:22 ` Luciano Coelho
2010-07-14 16:34 ` Pablo Neira Ayuso
2010-07-15 9:05 ` Patrick McHardy
2010-07-15 9:18 ` Luciano Coelho
2010-07-13 13:28 ` Samuel Ortiz
2010-07-13 14:57 ` [PATCH v2] " Samuel Ortiz
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=1279027474.12673.61.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sameo@linux.intel.com \
--cc=xiaosuo@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 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.