From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id E13FF1FF14F for ; Fri, 08 May 2026 18:39:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BCDD41FE95; Fri, 8 May 2026 18:39:28 +0200 (CEST) Message-ID: <55c370b6-f6d1-40ae-93c1-8876dba60e04@proxmox.com> Date: Fri, 8 May 2026 18:39:25 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH access-control/cluster/manager/network/proxmox{-ve-rs,-perl-rs} v5 00/46] Add support for route maps / prefix lists to SDN To: Lukas Sichert , pve-devel@lists.proxmox.com References: <20260505153720.412180-1-s.hanreich@proxmox.com> Content-Language: en-US From: Stefan Hanreich In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.632 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: OG6M52V3GYJK3WUCZOAWNL7UBBX7S26D X-Message-ID-Hash: OG6M52V3GYJK3WUCZOAWNL7UBBX7S26D 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 5/7/26 1:55 PM, Lukas Sichert wrote: > Here I ran into a problem though. I configured a prefix list with > Prefix: 10.0.10.0/22 > Prefix<=:21 > This is of course wrong, but it is not checked, so applying it is > possible. Here maybe a check in the frontend would be useful. > After applying I got a warning and even after correcting the prefix list > the warning did not go away. After deleting and reconfiguring the list > it worked again, but apparently, when adding Prefix<=:, it is only > possible to alter the value, not delete it. Deleting will just be > ignored. Thanks for the report, should be fixed in the v6!