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 80E7F1FF179 for ; Wed, 10 Dec 2025 20:37:54 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8B9304694; Wed, 10 Dec 2025 20:38:33 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Wed, 10 Dec 2025 20:38:25 +0100 Message-Id: <176539545735.1482544.14754067073553298647.b4-ty@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20251210184247.448937-4-s.hanreich@proxmox.com> References: <20251210184247.448937-1-s.hanreich@proxmox.com> <20251210184247.448937-4-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1765395502887 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.021 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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 pve-network 1/1] fix #6806: vlan: qinq: fix bridge port detection 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 Wed, 10 Dec 2025 19:42:45 +0100, Stefan Hanreich wrote: > When creating a vlan zone and vnet, pve-network looks at all the > physical bridge ports (slaves) and adds them to the generated vlan > bridge. The zone plugin gets all the bridge interfaces using > `/sys/class/net` and then filters them using a regex. With the > introduction of network interface pinning, the restrictions on network > interface names have gotten more liberal - they're not required to > have specific prefixes anymore. The check for physical interfaces in > the zones plugin needs to be adjusted to reflect those changes, > otherwise the generated SDN configuration does not contain any pinned > physical ports and therefore doesn't work. > > [...] Applied, but resolved conflict with selecting a branch point after the perl tidy commit, as that makes future backports much easier, thanks! [1/1] fix #6806: vlan: qinq: fix bridge port detection commit: bb7142117c72214ed4b7e4c99ce30ab837333558 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel