From: Andreas Herz <andi@geekosphere.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE]: Release of nftables 0.099
Date: Tue, 21 Jan 2014 12:59:09 +0100 [thread overview]
Message-ID: <20140121115909.GR5409@kvmbude> (raw)
In-Reply-To: <20140120131132.GA32427@macbook.localnet>
First of all thanks for the release and ongoing work!
On 20/01/14 at 13:11, Patrick McHardy wrote:
> nftables features native support for sets and dictionaries of arbitrary
> types, support for many different protocols, meta data types, connection
> tracking, NAT, logging, atomic incremental and full ruleset updates,
> a netlink API with notification support, a format grammar, a compatiblity
> layer for iptables/ip6tables and more.
Does the native set support also include sets with timeout, like the
ipset maintained by Jozsef?
Or is there any plan to introduce this feature into nftables or just use
ipset and make it nftables compatible?
Since i'm using a patched version of ipset i would like to know the
future related to that feature :)
Thanks
--
Andreas Herz
next prev parent reply other threads:[~2014-01-21 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 13:11 [ANNOUNCE]: Release of nftables 0.099 Patrick McHardy
2014-01-20 23:38 ` Release of nftables-plus 0.099 Jan Engelhardt
2014-01-20 23:41 ` [netfilter-core] " Patrick McHardy
2014-01-21 0:00 ` Jan Engelhardt
2014-01-21 0:26 ` Patrick McHardy
2014-01-21 11:59 ` Andreas Herz [this message]
2014-01-21 12:14 ` [ANNOUNCE]: Release of nftables 0.099 Patrick McHardy
2014-01-21 12:24 ` Andreas Herz
2014-01-21 12:32 ` Patrick McHardy
2014-01-21 12:43 ` Andreas Herz
2014-01-21 12:49 ` Patrick McHardy
2014-01-21 13:12 ` Jozsef Kadlecsik
2014-01-21 13:27 ` Patrick McHardy
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=20140121115909.GR5409@kvmbude \
--to=andi@geekosphere.org \
--cc=kaber@trash.net \
--cc=netfilter@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.