From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 0/4] Add support for 8021.AD frame matching
Date: Thu, 1 Apr 2021 16:08:42 +0200 [thread overview]
Message-ID: <20210401140846.24452-1-fw@strlen.de> (raw)
This allows to match vlan frames with 8021.AD ("QinQ") type.
Plan 'vlan id 1' will imply 8021Q, just as before, so explicit
type specification is needed.
This in turn makes it necessary to extend dependency removal so that
it will not auto-remove 8021ad check.
Add test case to make sure depdenencies are generated correctly,
this includes checks for 'vlan id 2' in a 'vlan id 1' vlan tag stack.
Florian Westphal (4):
src: vlan: allow matching vlan id insider 802.1ad frame
proto: add 8021ad as mnemonic for IEEE 802.1AD (0x88a8) ether type
payload: be careful on vlan dependency removal
tests: add 8021.AD vlan test cases
src/payload.c | 29 ++++-
src/proto.c | 4 +
src/scanner.l | 1 +
tests/py/bridge/vlan.t | 5 +
tests/py/bridge/vlan.t.json | 176 ++++++++++++++++++++++++++
tests/py/bridge/vlan.t.json.output | 173 +++++++++++++++++++++++++
tests/py/bridge/vlan.t.payload | 45 +++++++
tests/py/bridge/vlan.t.payload.netdev | 51 ++++++++
8 files changed, 481 insertions(+), 3 deletions(-)
--
2.26.3
next reply other threads:[~2021-04-01 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:08 Florian Westphal [this message]
2021-04-01 14:08 ` [PATCH nft 1/4] src: vlan: allow matching vlan id insider 802.1ad frame Florian Westphal
2021-04-01 14:08 ` [PATCH nft 2/4] proto: add 8021ad as mnemonic for IEEE 802.1AD (0x88a8) ether type Florian Westphal
2021-04-01 14:08 ` [PATCH nft 3/4] payload: be careful on vlan dependency removal Florian Westphal
2021-04-01 14:08 ` [PATCH nft 4/4] tests: add 8021.AD vlan test cases Florian Westphal
2021-04-02 10:54 ` [PATCH nft 5/4] proto: replace vlan ether type with 8021q Florian Westphal
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=20210401140846.24452-1-fw@strlen.de \
--to=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).