From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH ifupdown2 1/1] d/patches: allow subinterfaces on bond members
Date: Mon, 27 Oct 2025 15:32:11 +0100 [thread overview]
Message-ID: <176157552726.3826005.15533301798214910781.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250930140948.265119-1-s.hanreich@proxmox.com>
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
prev parent reply other threads:[~2025-10-27 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 14:09 [pve-devel] " Stefan Hanreich
2025-10-27 14:32 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176157552726.3826005.15533301798214910781.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox