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 31FF41FF13B for ; Wed, 06 May 2026 02:09:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6C09E10F63; Wed, 6 May 2026 02:09:39 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Subject: applied: [PATCH access-control/cluster/manager/network/proxmox{-ve-rs,-perl-rs} v5 00/46] Add support for route maps / prefix lists to SDN Date: Wed, 6 May 2026 02:08:13 +0200 Message-ID: <177802597082.2857170.7993378482662720202.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260505153720.412180-1-s.hanreich@proxmox.com> References: <20260505153720.412180-1-s.hanreich@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: 1778026036013 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: 4TWHHEYG37SYU43A3QI6JVFJKEWDOXT3 X-Message-ID-Hash: 4TWHHEYG37SYU43A3QI6JVFJKEWDOXT3 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 Tue, 05 May 2026 17:36:28 +0200, Stefan Hanreich wrote: > ## Introduction > > This patch adds support for managing route maps and prefix lists to the SDN > stack. With this patch series, route maps can be applied to the BGP and EVPN > controller for incoming / outgoing route filtering. Additionally, prefix lists > can be used to filter routes that should be installed by a fabric into the > kernel routing table, overriding the default behavior of only installing routes > from the configured IP prefix. There are currently some other features in > development that would make use of route maps as well, namely: > > [...] Applied, thanks! [1/1] permissions: add ACL path for prefix-lists and route-maps commit: 7dd60724f75c18d6502d474bd6a5a28971ca1bae