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 EED251FF14C for ; Fri, 15 May 2026 07:03:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CDE86AF9C; Fri, 15 May 2026 07:03:13 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Gabriel Goller Subject: applied: [PATCH manager/network v2 0/4] Extend prefix-list CIDR range Date: Fri, 15 May 2026 07:02:47 +0200 Message-ID: <177882100649.373143.14192193277075190166.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260513083430.63529-1-g.goller@proxmox.com> References: <20260513083430.63529-1-g.goller@proxmox.com> 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: 1778821384330 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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: DHCBTZQ3BP55654J72PZHZ52AEH754UE X-Message-ID-Hash: DHCBTZQ3BP55654J72PZHZ52AEH754UE X-MailFrom: t.lamprecht@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 Wed, 13 May 2026 10:34:19 +0200, Gabriel Goller wrote: > This is a follow-up on the route-maps and prefix-list series by Stefan. > The goal is to extend the CIDR range on the prefix-list, making it possible to > allow prefixes such as 0.0.0.0/0, which is a classic "allow-all". > > The current IP64CIDRAddress(ui)/CIDR(api) format only allows a minimum of /8 CIDR. In order > to keep it backwards compatible and avoid accidentally breaking migration or > replication, create a new format. > > [...] Applied, thanks! [1/2] sdn: prefix-list: allow full prefix CIDR range commit: 15e78164ef6b6256ed64885817d2582d93610742 [2/2] sdn: add full-range CIDR JSON schema formats commit: 24b625249a25a944efbe21509b35e8a7545a54bd