From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Jan Engelhardt <jengelh@medozas.de>
Cc: "kaber@trash.net" <kaber@trash.net>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] netfilter: xtables: inclusion of xt_condition
Date: Fri, 16 Jul 2010 14:31:22 +0300 [thread overview]
Message-ID: <1279279882.1603.56.camel@powerslave> (raw)
In-Reply-To: <alpine.LSU.2.01.1007161320310.14608@obet.zrqbmnf.qr>
On Fri, 2010-07-16 at 13:20 +0200, ext Jan Engelhardt wrote:
> On Friday 2010-07-16 13:10, Luciano Coelho wrote:
> >Jan Engelhardt <jengelh@medozas.de> writes:
> >> On Thursday 2010-04-22 13:14, Patrick McHardy wrote:
> >>
> >> > This looks better, thanks. A few remaining questions about things
> >> > I missed previously:
> >>
> >> Will deal with it shortly.
> >
> >Are you planning to resend this patch with the changes Patrick
> >suggested?
>
> I can try.
Cool, thanks!
> >As you may have seen in my earlier rfc email, I'm interested in
> >something similar to the condition match. I'm not sure whether the best
> >approach is to create a CONDITION target where we can set the condition
> >variable in the iptables itself or if it is better to create a new
> >"variable match" and an accompanying "VARIABLE target" that keeps the
> >variables in memory, instead of using procfs.
>
> procfs is in memory :)
Yes, of course, but I meant without exporting it to procfs. ;) That
would probably make the code a lot simpler (actually I can't imagine a
simpler match/target than a "variable" match/target ;)
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-07-16 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 11:10 [PATCH] netfilter: xtables: inclusion of xt_condition Luciano Coelho
2010-07-16 11:20 ` Jan Engelhardt
2010-07-16 11:31 ` Luciano Coelho [this message]
2010-07-16 11:54 ` Jan Engelhardt
2010-07-16 12:16 ` Luciano Coelho
2010-07-16 19:14 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2010-07-17 6:32 Luciano.Coelho
2010-04-21 13:33 nf-next: condition Jan Engelhardt
2010-04-21 13:33 ` [PATCH] netfilter: xtables: inclusion of xt_condition Jan Engelhardt
2010-04-21 13:39 ` Patrick McHardy
2010-04-22 0:05 ` Jan Engelhardt
2010-04-22 10:55 ` Patrick McHardy
2010-04-22 11:14 ` Patrick McHardy
2010-04-22 11:24 ` Patrick McHardy
2010-04-22 11:27 ` Jan Engelhardt
2010-04-22 11:29 ` Patrick McHardy
2010-04-22 11:33 ` Jan Engelhardt
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=1279279882.1603.56.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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.