From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id B6E9F1FF142 for ; Fri, 05 Jun 2026 13:48:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BFA9F177A8; Fri, 5 Jun 2026 13:48:50 +0200 (CEST) From: Lukas Sichert To: pve-devel@lists.proxmox.com Subject: [PATCH manager 3/3] fix #5066: reload networking: flush PROXMOX-SDN iptables chain at reload Date: Fri, 5 Jun 2026 13:48:04 +0200 Message-ID: <20260605114810.43030-4-l.sichert@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260605114810.43030-1-l.sichert@proxmox.com> References: <20260605114810.43030-1-l.sichert@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1780660057834 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.300 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: EDBJ6C75SKKUBAYGI2F7SU5EEQPAFYOX X-Message-ID-Hash: EDBJ6C75SKKUBAYGI2F7SU5EEQPAFYOX X-MailFrom: l.sichert@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 CC: Lukas Sichert X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: With the addition of a separate PROXMOX-SDN iptable chain it is now possible to flush this distinct chain, without affecting unreated POSTROUTING rules set by the user. Flush old rules by running 'iptables -t nat -F PROXMOX-SDN' at the end of the reload_network_config API call, before executing 'ifreload -a'. The reload then adds the currently valid rules again. Signed-off-by: Lukas Sichert --- .codex | 0 PVE/API2/Network.pm | 3 +++ 2 files changed, 3 insertions(+) create mode 100644 .codex diff --git a/.codex b/.codex new file mode 100644 index 00000000..e69de29b diff --git a/PVE/API2/Network.pm b/PVE/API2/Network.pm index c5863ca7..a8ec88a4 100644 --- a/PVE/API2/Network.pm +++ b/PVE/API2/Network.pm @@ -932,6 +932,9 @@ __PACKAGE__->register_method({ print "$2 : $line \n"; } }; + PVE::Tools::run_command(['iptables', '-t', 'nat', '-F', 'PROXMOX-SDN'], noerr => 1); + PVE::Tools::run_command(['ip6tables', '-t', 'nat', '-F', 'PROXMOX-SDN'], + noerr => 1); PVE::Tools::run_command(['ifreload', '-a'], errfunc => $err); if (defined($regenerate_frr)) { -- 2.47.3