From: Dash Four <mr.dash.four@googlemail.com>
To: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 00/13] ipset patches for nf-next
Date: Sat, 27 Apr 2013 21:07:51 +0100 [thread overview]
Message-ID: <517C3017.8090803@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1304272042070.1511@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
>> Jozsef, are these features already supported in userspace or are you going to
>> release a separate version?
>>
>
> It's already supported in userspace in the main branch of the git tree.
Got it, thanks Jozsef, though I can't see any updates to the ipset
branch of the netfilter.org tree (https://git.netfilter.org/ipset) -
last update is showing 13 days ago.
> As the patch for the userspace part of the set match is committed in the
> iptables git tree, there'll come the new ipset release.
>
OK, good to know. I see that with the new patches you have expanded the
ipset data structure, which is also good - I could now fit all of my
"custom" changes without resorting to dark-art gimmicks as I did up
until now.
next prev parent reply other threads:[~2013-04-27 20:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 12:50 [PATCH 00/13] ipset patches for nf-next Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 01/13] netfilter: ipset: Make possible to test elements marked with nomatch Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 02/13] netfilter: ipset: Move often used IPv6 address masking function to header file Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 03/13] netfilter: ipset: Introduce extensions to elements in the core Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 04/13] netfilter: ipset: Unified bitmap type generation Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 05/13] netfilter: ipset: Bitmap types using the unified code base Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 06/13] netfilter: ipset: Unified hash type generation Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 07/13] netfilter: ipset: Hash types using the unified code base Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 08/13] netfilter: ipset: list:set type using the extension interface Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 09/13] netfilter: ipset: Introduce the counter extension in the core Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 10/13] netfilter: ipset: The bitmap types with counter support Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 11/13] netfilter: ipset: The hash " Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 12/13] netfilter: ipset: The list:set type " Jozsef Kadlecsik
2013-04-27 12:50 ` [PATCH 13/13] netfilter: ipset: set match: add support to match the counters Jozsef Kadlecsik
2013-04-27 17:33 ` Pablo Neira Ayuso
2013-04-27 18:36 ` Jozsef Kadlecsik
2013-04-27 12:54 ` [PATCH 00/13] ipset patches for nf-next Dash Four
2013-04-27 18:44 ` Jozsef Kadlecsik
2013-04-27 20:07 ` Dash Four [this message]
2013-04-27 20:15 ` Jozsef Kadlecsik
2013-04-27 17:42 ` Pablo Neira Ayuso
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=517C3017.8090803@googlemail.com \
--to=mr.dash.four@googlemail.com \
--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 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).