From: Pablo Neira Ayuso <pablo@netfilter.org>
To: wenxu@ucloud.cn
Cc: fw@strlen.de, netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next v2 1/2] netfilter: nft_meta: add NFT_META_BRI_PVID support
Date: Wed, 26 Jun 2019 12:30:45 +0200 [thread overview]
Message-ID: <20190626103045.fn6gq2mptrotpju4@salvia> (raw)
In-Reply-To: <20190626090116.3qjmlnd5egeifozq@salvia>
On Wed, Jun 26, 2019 at 11:01:16AM +0200, Pablo Neira Ayuso wrote:
> On Thu, Jun 20, 2019 at 09:17:39AM +0800, wenxu@ucloud.cn wrote:
> > From: wenxu <wenxu@ucloud.cn>
> >
> > nft add table bridge firewall
> > nft add chain bridge firewall zones { type filter hook prerouting priority - 300 \; }
> > nft add rule bridge firewall zones counter ct zone set vlan id map { 100 : 1, 200 : 2 }
> >
> > As above set the bridge port with pvid, the received packet don't contain
> > the vlan tag which means the packet should belong to vlan 200 through pvid.
> > With this pacth user can get the pvid of bridge ports.
> >
> > So add the following rule for as the first rule in the chain of zones.
> >
> > nft add rule bridge firewall zones counter meta brvlan set meta brpvid
>
> Applied, thanks.
https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git/commit/?id=da4f10a4265b109fbdb77d5995236e0843e4a26d
This patch is applied.
2/2 is not, until we finish a bit of discussion on where to go.
Thanks.
prev parent reply other threads:[~2019-06-26 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 1:17 [PATCH nf-next v2 1/2] netfilter: nft_meta: add NFT_META_BRI_PVID support wenxu
2019-06-20 1:17 ` [PATCH nf-next v2 2/2] netfilter: nft_meta: Add NFT_META_BRI_VLAN support wenxu
2019-06-26 9:01 ` Pablo Neira Ayuso
2019-06-26 10:29 ` Pablo Neira Ayuso
2019-06-26 12:42 ` wenxu
2019-06-26 12:57 ` Pablo Neira Ayuso
2019-06-25 9:23 ` [PATCH nf-next v2 1/2] netfilter: nft_meta: add NFT_META_BRI_PVID support wenxu
2019-06-25 9:54 ` Pablo Neira Ayuso
2019-06-26 9:01 ` Pablo Neira Ayuso
2019-06-26 10:30 ` 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=20190626103045.fn6gq2mptrotpju4@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).