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 779C61FF0B3 for ; Fri, 25 Sep 2026 11:45:07 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 97083216CA; Fri, 25 Sep 2026 11:45:03 +0200 (CEST) Date: Fri, 25 Sep 2026 11:44:23 +0200 From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: superseded: [PATCH firewall/manager v2 0/9] allow updating references when renaming/deleting firewall objects Message-ID: <6tvmnnnamupdvgpeifnus5flab46pmy262rbquleok2szwnuzn@zhey74ezkiin> References: <20260818133413.450776-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260818133413.450776-1-a.bied-charreton@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1790329464319 X-SPAM-LEVEL: Spam detection results: 0 AWL 1.407 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: UAMU6KSDJ44JZO4YCPR3WGCX472FLRVE X-Message-ID-Hash: UAMU6KSDJ44JZO4YCPR3WGCX472FLRVE X-MailFrom: a.bied-charreton@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 Tue, Aug 18, 2026 at 03:34:04PM +0200, Arthur Bied-Charreton wrote: > Renaming or deleting a firewall object (IPSet or alias) that is still > referenced currently leaves dangling references behind. The firewall > then fails to parse the affected rules, which become inactive without > any error visible from the UI. > [...] superseded by: https://lore.proxmox.com/pve-devel/20260925094230.844917-1-a.bied-charreton@proxmox.com/T/#t