From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id B4E101FF0AB for ; Wed, 23 Sep 2026 21:15:41 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3C00F2160D; Wed, 23 Sep 2026 21:15:39 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH proxmox-firewall] nftables: add support for mark-keyed verdict maps Date: Wed, 23 Sep 2026 21:15:26 +0200 Message-ID: <179019092349.3587707.17451440492610623352.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260827131756.1413841-1-h.laimer@proxmox.com> References: <20260827131756.1413841-1-h.laimer@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: 1790190935757 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.730 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: UMN42UCF6LNDSB5WUIKD26ACN7J2TXUD X-Message-ID-Hash: UMN42UCF6LNDSB5WUIKD26ACN7J2TXUD 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 Thu, 27 Aug 2026 15:17:56 +0200, Hannes Laimer wrote: > nftables sets and maps can be keyed by the packet mark, but the mark > element type has not yet been exposed by proxmox-nftables. A vmap > statement could so far only be parsed, not constructed, so the only ones > in use come from the static ruleset skeleton. Add both to the lib. Applied, thanks! [1/1] nftables: add support for mark-keyed verdict maps commit: f558dc863dd2ac072438d4cc655a7033fcae67fb