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 D667E1FF15E for ; Mon, 27 Oct 2025 15:35:45 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F0AF385B8; Mon, 27 Oct 2025 15:36:15 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Mon, 27 Oct 2025 15:32:11 +0100 Message-ID: <176157552726.3826005.15533301798214910781.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250930140948.265119-1-s.hanreich@proxmox.com> References: <20250930140948.265119-1-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1761575761409 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.025 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 ifupdown2 1/1] d/patches: allow subinterfaces on bond members 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 Tue, 30 Sep 2025 16:09:46 +0200, Stefan Hanreich wrote: > ifupdown2 commit c50aff4f702ea366955552865aceab5b3735513a introduced a > change that disallows creating subinterfaces (e.g. VLAN) on top of > interfaces that are members of a bond. > > This breaks a setup that is common to users utilizing storage boxes > via iSCSI multipath where a bond is defined on two interfaces and used > for e.g. VM traffic, but a specific VLAN is configured on the bond > members themselves and used as storage network. An example ifupdown2 > configuration might look like this: > > [...] Applied, thanks! I amended the commit to avoid reverting the hunk that fixed a grammar error in a log message and reworked the commit subject, especially the "d/patches" tag is not really useful for devs or end-users here. [1/1] d/patches: allow subinterfaces on bond members commit: f55f1190b988465be184f44f3f6a190354ab50ae _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel