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 47EBE1FF0E5 for ; Wed, 15 Jul 2026 14:24:47 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 75DEA21419; Wed, 15 Jul 2026 14:24:46 +0200 (CEST) From: Dominik Csapak To: pve-devel@lists.proxmox.com, Lukas Sichert Subject: applied: [PATCH manager v3 0/2] ui: fabrics: handle unsupported IP properties for BGP interfaces Date: Wed, 15 Jul 2026 14:24:04 +0200 Message-ID: <178411821561.2916317.4171483330747393973.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260715081519.29721-1-l.sichert@proxmox.com> References: <20260715081519.29721-1-l.sichert@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.314 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_LOW -0.7 Sender listed at https://www.dnswl.org/, low 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: 5ZK532JGVKP3V3NTOBWVRCEZXC4JKF5P X-Message-ID-Hash: 5ZK532JGVKP3V3NTOBWVRCEZXC4JKF5P X-MailFrom: d.csapak@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, 15 Jul 2026 10:15:14 +0200, Lukas Sichert wrote: > BGP unnumbered interfaces do not support per-interface IPv4 or IPv6 > addresses. The UI already hid the IPv6 column through a declarative > support flag, but IPv4 needed a protocol-specific initComponent() > override that manually filtered the base column list. > > This series first adjusts the IPv4 column handling to make it optional > via a declarative support flag. It then uses the IPv4/IPv6 support flags > to avoid sending unsupported ip/ip6 interface data to the backend. > > [...] Applied, thanks! [1/2] ui: fabrics: make IPv4 interface column optional commit: 79fc8f141661dc15f9352a0d00f53faae52eb404 [2/2] ui: fabrics: skip unsupported IP properties on submit commit: cd09954e2915d60f636dfa8fd3416ca425566bbb