From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 1CBE91FF0AF for ; Fri, 20 Nov 2026 16:28:32 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 13E31217A7; Fri, 20 Nov 2026 16:28:24 +0100 (CET) From: Stefan Hanreich 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 Message-ID: <20261120152811.473269-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795188499444 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.217 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: HWVN2PO47JR4BDF4DDECYUKO5RQX67JL X-Message-ID-Hash: HWVN2PO47JR4BDF4DDECYUKO5RQX67JL X-MailFrom: s.hanreich@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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