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 8C7871FF13C for ; Thu, 25 Jun 2026 17:51:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B076415233; Thu, 25 Jun 2026 17:51:29 +0200 (CEST) Message-ID: Date: Thu, 25 Jun 2026 17:51:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC manager/network v2 0/3] fix #5066: make generated snat rules flushable To: pve-devel@lists.proxmox.com References: <20260623133721.29483-1-l.sichert@proxmox.com> <4c57df22-f070-4da4-970a-b79c7c65bb13@proxmox.com> Content-Language: en-US From: Stefan Hanreich In-Reply-To: <4c57df22-f070-4da4-970a-b79c7c65bb13@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.594 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: ZZLEQ6YVNCFGZSAPY4B4FZPM3JQXNKZS X-Message-ID-Hash: ZZLEQ6YVNCFGZSAPY4B4FZPM3JQXNKZS 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: On 6/25/26 5:44 PM, Stefan Hanreich wrote: [snip] > The only way to work around this I can think of is by creating a new > chain with a different name (PROXMOX-SDN-new) and create the ruleset > there. Afterwards, insert the jump to the new chain before the old chain > in the NAT table and finally delete the rule jumping to the old chain. > Afterwards, rename the PROXMOX-SDN-new chain to PROXMOX-SDN via the -E > option of iptables. Just noticed, with that approach configuration wouldn't survive a reboot :/. But we could possibly invert the logic and rename the old chain to PROXMOX-SDN-old and leave the current config as-is. Then simply remove the PROXMOX-SDN-old chain inside the reload network configuration function. [snip]