From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: nf-devel <netfilter-devel@vger.kernel.org>
Subject: Re: Implicit flow tables can't be listed
Date: Thu, 23 Jun 2016 12:11:14 +0200 [thread overview]
Message-ID: <20160623101114.GA6248@salvia> (raw)
In-Reply-To: <20160622122547.GA10213@breakpoint.cc>
On Wed, Jun 22, 2016 at 02:25:47PM +0200, Florian Westphal wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > How can we actually relate the rule with the flow table if we have
> > several anonymous flow tables?
>
> nft list table filter
> table ip filter {
> chain input {
> type filter hook input priority 0; policy accept;
> flow table __ft0 { ip saddr counter packets 0 bytes 0}
> flow table __ft1 { ip daddr counter packets 0 bytes 0}
> }
>
> ... so the internal name will be shown.
OK, then enhance the scanner to catch __ and run tests to validate. I
don't think this break anything.
prev parent reply other threads:[~2016-06-23 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 10:29 Implicit flow tables can't be listed Florian Westphal
2016-06-22 12:15 ` Pablo Neira Ayuso
2016-06-22 12:25 ` Florian Westphal
2016-06-23 10:11 ` Pablo Neira Ayuso [this message]
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=20160623101114.GA6248@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--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).