From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox{-ve-rs,-firewall} 0/4] sdn: zone VRF conntrack zones: follow-ups
Date: Fri, 20 Nov 2026 16:28:05 +0100 [thread overview]
Message-ID: <20261120152811.473269-1-s.hanreich@proxmox.com> (raw)
The VRF device of a zone is only created on the nodes of the zone, but
proxmox-firewall set the conntrack zone for every interface with the
name of the VRF device and the interfaces enslaved to it on all nodes.
So on a node that is not part of the zone, a manually created interface
with that name and its members got the conntrack zone as well.
proxmox-ve-config now reads the nodes of a zone from the running config,
and the conntrack zones are only applied for the zones that exist on the
local node.
Additionally, proxmox-firewall queried the network interfaces twice when
generating the ruleset, once for the altname mapping and once for the
conntrack zones of bridges in zone VRFs. They are now queried once.
Dependencies:
proxmox-firewall needs proxmox-ve-config.
proxmox-ve-rs:
Stefan Hanreich (2):
sdn: config: read the nodes of zones from the running config
sdn: conntrack: only map the VRFs of zones that exist on the node
proxmox-ve-config/src/sdn/config.rs | 18 ++++++++
proxmox-ve-config/src/sdn/conntrack.rs | 26 ++++++-----
proxmox-ve-config/tests/sdn/main.rs | 63 +++++++++++++++++++++++++-
3 files changed, 94 insertions(+), 13 deletions(-)
proxmox-firewall:
Stefan Hanreich (2):
firewall: config: query the network interfaces only once
firewall: sdn: only apply the conntrack zones of zones on this node
proxmox-firewall/Cargo.toml | 2 +-
proxmox-firewall/src/bin/proxmox-firewall.rs | 9 +++-
proxmox-firewall/src/config.rs | 24 ++++------
proxmox-firewall/src/sdn.rs | 46 +++++++++++++-------
proxmox-firewall/tests/integration_tests.rs | 6 +--
5 files changed, 47 insertions(+), 40 deletions(-)
Summary over all repositories:
8 files changed, 141 insertions(+), 53 deletions(-)
--
Generated by murpp 0.12.1
next reply other threads:[~2026-11-20 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 15:28 Stefan Hanreich [this message]
2026-11-20 15:28 ` [PATCH proxmox-ve-rs 1/4] sdn: config: read the nodes of zones from the running config Stefan Hanreich
2026-11-20 15:28 ` [PATCH proxmox-ve-rs 2/4] sdn: conntrack: only map the VRFs of zones that exist on the node Stefan Hanreich
2026-11-20 15:28 ` [PATCH proxmox-firewall 3/4] firewall: config: query the network interfaces only once Stefan Hanreich
2026-11-20 15:28 ` [PATCH proxmox-firewall 4/4] firewall: sdn: only apply the conntrack zones of zones on this node Stefan Hanreich
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=20261120152811.473269-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 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.