netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Jan Engelhardt <jengelh@medozas.de>
Cc: ext Patrick McHardy <kaber@trash.net>,
	"netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Changli Gao <xiaosuo@gmail.com>
Subject: Re: [RFC] setting up throughput threshold indications to userspace
Date: Mon, 19 Jul 2010 08:30:23 +0300	[thread overview]
Message-ID: <1279517423.7097.2.camel@powerslave> (raw)
In-Reply-To: <alpine.LSU.2.01.1007162127090.22666@obet.zrqbmnf.qr>

On Fri, 2010-07-16 at 21:27 +0200, ext Jan Engelhardt wrote:
> On Friday 2010-07-16 15:10, Luciano Coelho wrote:
> >> > There is one problem with this solution, which is that it works in a
> >> > per-connection basis (due to CONNMARK).  This is not exactly what I
> >> > want.  I need to have this on a per-ruleset basis.  For that, I need to
> >> > have a MARK (variable?) which can be set independently of connections or
> >> > packets.  This is similar to the proposed condition match, but what is
> >> > missing there is a way to set the condition with iptables itself,
> >> > without requiring the userspace to change the procfs file.  This could
> >> > probably be achieved with a "CONDITION" target or something similar.
> >> > Any ideas?
> >> 
> >> Sounds useful.
> >
> >Okay, this was the kind of confirmation I wanted before jumping into the
> >implementation. ;) I'll implement this target soon.
> 
> My suggestion to have it combined with xt_condition.

Yes, I also think that is the best idea.  I'll implement a CONDITION
target that will work together with the condition match.  For now I'll
use the non-final version you submitted some time ago.


-- 
Cheers,
Luca.


  reply	other threads:[~2010-07-19  5:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16  8:20 [RFC] setting up throughput threshold indications to userspace Luciano Coelho
2010-07-16 13:01 ` Patrick McHardy
2010-07-16 13:10   ` Luciano Coelho
2010-07-16 19:27     ` Jan Engelhardt
2010-07-19  5:30       ` Luciano Coelho [this message]
2010-08-16 13:40         ` Luciano Coelho
2010-08-16 13:51           ` Changli Gao
2010-08-16 14:01             ` Luciano Coelho
2010-08-16 14:13               ` Changli Gao
2010-08-16 14:26                 ` Luciano Coelho
2010-08-16 15:19               ` Jan Engelhardt
2010-08-17  5:27                 ` Luciano Coelho
2010-08-16 14:26           ` Changli Gao
2010-08-16 14:32             ` Luciano Coelho

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=1279517423.7097.2.camel@powerslave \
    --to=luciano.coelho@nokia.com \
    --cc=jengelh@medozas.de \
    --cc=kaber@trash.net \
    --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 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).