From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Brian Allen Vanderburg II <brianvanderburg2@aim.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables with ipset combined types
Date: Wed, 29 Jan 2014 10:30:11 +0100 [thread overview]
Message-ID: <20140129093010.GA4332@localhost> (raw)
In-Reply-To: <52E8AD76.5050808@aim.com>
On Wed, Jan 29, 2014 at 02:27:50AM -0500, Brian Allen Vanderburg II wrote:
> I use ipset for my setup to simplify certain iptables rules. I have
> rules to allow trusted networks and trusted services using two different
> sets. The services set is a hash:net,port set, and the network set its
> a hash:net,iface set. Is it planned to have sets that can contain
> multiple value entries in nftables?
Yes, some bits are missing in the kernel, we'll have support for
multi-dimensional keys in sets at some point.
next prev parent reply other threads:[~2014-01-29 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 7:27 nftables with ipset combined types Brian Allen Vanderburg II
2014-01-29 9:30 ` Pablo Neira Ayuso [this message]
2014-01-29 11:34 ` Patrick Schaaf
2014-01-29 11:48 ` Arturo Borrero Gonzalez
2014-02-02 23:57 ` Pablo Neira Ayuso
2014-02-03 20:28 ` 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=20140129093010.GA4332@localhost \
--to=pablo@netfilter.org \
--cc=brianvanderburg2@aim.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).