From: Eric Woudstra <ericwouds@gmail.com>
To: Michal Ostrowski <mostrows@earthlink.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Eric Woudstra <ericwouds@gmail.com>
Subject: [PATCH v10 nf-next 0/3] Add nf_flow_encap_push() for xmit direct
Date: Sat, 15 Mar 2025 20:59:07 +0100 [thread overview]
Message-ID: <20250315195910.17659-1-ericwouds@gmail.com> (raw)
To have the ability to handle xmit direct with outgoing encaps in the
bridge fastpass bypass, we need to be able to handle them without going
through vlan/pppoe devices.
So I've applied, amended and squashed wenxu's patch-set.
This patch also makes it possible to egress from vlan-filtering brlan to
lan0 with vlan tagged packets, if the bridge master port is doing the
vlan tagging, instead of a vlan-device, as seen in the figure below.
Without this patch, this is currently not possible in the
forward-fastpath.
forward fastpath bypass
.----------------------------------------.
/ \
| IP - forwarding |
| / \ v
| / wan ...
| /
| |
| |
| +-------------------------------+
| | untagged |
| | to |
| | vlan 1 |
| | |
| | brlan (vlan-filtering) |
| +---------------+ |
| | DSA-SWITCH | |
| | | vlan 1 |
| | | to |
| | vlan 1 | untagged |
| +---------------+---------------+
. / \
------>lan0 wlan1
.
.
.
.
.
^
vlan 1 tagged packets
Added patch to eliminate array of flexible structures warning.
Added patch to clean up structures.
Split from patch-set: bridge-fastpath and related improvements v9
Eric Woudstra (3):
net: pppoe: avoid zero-length arrays in struct pppoe_hdr
netfilter: nf_flow_table_offload: Add nf_flow_encap_push() for xmit
direct
netfilter: flow: remove hw_outdev, out.hw_ifindex and out.hw_ifidx
drivers/net/ppp/pppoe.c | 2 +-
include/net/netfilter/nf_flow_table.h | 2 -
include/uapi/linux/if_pppox.h | 4 ++
net/netfilter/nf_flow_table_core.c | 1 -
net/netfilter/nf_flow_table_ip.c | 96 ++++++++++++++++++++++++++-
net/netfilter/nf_flow_table_offload.c | 2 +-
net/netfilter/nft_flow_offload.c | 10 +--
7 files changed, 102 insertions(+), 15 deletions(-)
--
2.47.1
next reply other threads:[~2025-03-15 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 19:59 Eric Woudstra [this message]
2025-03-15 19:59 ` [PATCH v10 nf-next 1/3] net: pppoe: avoid zero-length arrays in struct pppoe_hdr Eric Woudstra
2025-03-23 16:48 ` Simon Horman
2025-03-25 6:46 ` Eric Woudstra
2025-03-15 19:59 ` [PATCH v10 nf-next 2/3] netfilter: nf_flow_table_offload: Add nf_flow_encap_push() for xmit direct Eric Woudstra
2025-03-18 23:23 ` Pablo Neira Ayuso
2025-03-19 19:37 ` Eric Woudstra
2025-03-15 19:59 ` [PATCH v10 nf-next 3/3] netfilter: flow: remove hw_outdev, out.hw_ifindex and out.hw_ifidx Eric Woudstra
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=20250315195910.17659-1-ericwouds@gmail.com \
--to=ericwouds@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=mostrows@earthlink.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.