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 F1E5E1FF16B for ; Tue, 29 Jul 2025 09:38:18 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9960A95F2; Tue, 29 Jul 2025 09:39:43 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Tue, 29 Jul 2025 09:38:09 +0200 Message-ID: <175377468888.1957591.4182790303711225669.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250724093459.76397-1-s.hanreich@proxmox.com> References: <20250724093459.76397-1-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753774772518 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 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 Subject: [pve-devel] applied: [PATCH manager v2 0/4] improvements to proxmox-network-interface-pinning X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu, 24 Jul 2025 11:34:55 +0200, Stefan Hanreich wrote: > Several improvements to the network interface pinning tool: > * interfaces are now iterated according to ifindex > * output of the mapping is now sorted and less verbose > * users can now set a specific target name > * if has been introduced as an additional legal prefix > > Still looking into removing the PHYSICAL_NIC_RE altogether, but sending this > patch series as-is nevertheless for review / feedback. If I manage to remove the > PHYSICAL_NIC_RE in time, we could get rid of the constraints of prefix / > target-name altogether... > > [...] Applied, thanks! Made two small follow-up commits, one to adapt the 'prefix' parameter description (was copied from the interface parameter) and replacing the explicit check for the target-name -> interface parameter dependency with the built-in support from our JSON schema implementation. [1/4] network-interface-pinning: use ifindex as order for pinning commit: 595b69b02474e7ad8d159cf757249a691c1f7ebb [2/4] network-interface-pinning: improve printing mapping commit: e19c1f48b5d747eb0232e6616e2c938271bf3924 [3/4] network-interface-pinning: add target-name parameter commit: 63dddce3cb7c7b4adae5897376bf4aa09b14d61b [4/4] network-interface-pinning: add if prefix to list of allowed prefixes commit: 90057e0ab947804704de91dccab7b8d2b219373f _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel