From: Florian Westphal <fw@strlen.de>
To: wenxu@ucloud.cn
Cc: pablo@netfilter.org, dsahern@gmail.com, fw@strlen.de,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] netfilter: nft_meta: Add NFT_META_L3MASTER meta type
Date: Tue, 15 Jan 2019 12:17:38 +0100 [thread overview]
Message-ID: <20190115111738.luy6pmhkvbb42dio@breakpoint.cc> (raw)
In-Reply-To: <1547529039-26786-1-git-send-email-wenxu@ucloud.cn>
wenxu@ucloud.cn <wenxu@ucloud.cn> wrote:
> From: wenxu <wenxu@ucloud.cn>
> so with this patch userspace can add the 'don't re-do entire ruleset for vrf' policy
> itself like the following
>
> nft add rule firewall rules-all meta l3master true counter accept
I wonder if we need to support this also for output interface, and if
this should be specific to vrf or not.
Example:
meta iifl3master exists accept
meta oifl3master exists accept
or
meta iifkind "vrf" accept
meta oifkind "vrf" accept
(the latter could e.g. place rtnl_op ".kind" in the register)
Not sure if that would ever be useful beyond vrf.
next prev parent reply other threads:[~2019-01-15 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 5:10 [PATCH] netfilter: nft_meta: Add NFT_META_L3MASTER meta type wenxu
2019-01-15 11:17 ` Florian Westphal [this message]
2019-01-15 15:19 ` wenxu
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=20190115111738.luy6pmhkvbb42dio@breakpoint.cc \
--to=fw@strlen.de \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wenxu@ucloud.cn \
/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).