From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common/manager/network 0/4] trixie: fix VLAN handling on vlan-unaware bridges with pinned NIC names
Date: Wed, 10 Dec 2025 19:42:30 +0100 [thread overview]
Message-ID: <20251210184236.448600-1-s.hanreich@proxmox.com> (raw)
There were mainly two issues related to this:
* generating SDN configuration for VLAN and QinQ zones that use vlan-unaware
bridges
* tagging network devices of VMs on vlan-unaware bridges
In both cases the detection of the underlying physical ports relied on a regex,
that doesn't work with pinned names at all. Switch over to using `ip link` for
the detection of physical ports, since network interfaces can now have names
that do not need to have a specific prefix at all. For SDN, we add a new change
detection mechanism to `pve-sdn-commit`, that reloads the SDN configuration if
there is a vlan-unaware bridge used as the underlying bridge of a VLAN / QinQ
zone. This ensures that the network configuration gets regenerated properly
if pinning takes place, after a VLAN or QinQ zone have been created.
Dependencies:
pve-manager depends on pve-common
pve-network depends on pve-common
pve-common:
Stefan Hanreich (2):
fix #7118: fix bridge port detection when plugging netdev with vlan
iproute2: add helpers for detecting vlan-aware bridges
src/PVE/IPRoute2.pm | 32 ++++++++++++++++++++++++++++++++
src/PVE/Network.pm | 12 ++----------
2 files changed, 34 insertions(+), 10 deletions(-)
pve-manager:
Stefan Hanreich (1):
pve-sdn-commit: run for vlan/qinq zones on non-vlan-aware bridges
bin/pve-sdn-commit | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
pve-network:
Stefan Hanreich (1):
fix #6806: vlan: qinq: fix bridge port detection
src/PVE/Network/SDN/Zones/Plugin.pm | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
Summary over all repositories:
4 files changed, 58 insertions(+), 22 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-12-10 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 18:42 Stefan Hanreich [this message]
2025-12-10 18:42 ` [pve-devel] [PATCH pve-common 1/2] fix #7118: fix bridge port detection when plugging netdev with vlan Stefan Hanreich
2025-12-10 18:42 ` [pve-devel] [PATCH pve-common 2/2] iproute2: add helpers for detecting vlan-aware bridges Stefan Hanreich
2025-12-10 19:29 ` [pve-devel] applied: " Thomas Lamprecht
2025-12-10 18:42 ` [pve-devel] [PATCH pve-manager 1/1] pve-sdn-commit: run for vlan/qinq zones on non-vlan-aware bridges Stefan Hanreich
2025-12-10 18:42 ` [pve-devel] [PATCH pve-network 1/1] fix #6806: vlan: qinq: fix bridge port detection Stefan Hanreich
2025-12-10 19:32 ` [pve-devel] applied: " Thomas Lamprecht
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=20251210184236.448600-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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