all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH common] fix #7193: allow vlan-interfaces as physical bridge ports
Date: Wed, 31 Dec 2025 08:11:08 +0100	[thread overview]
Message-ID: <176716506419.2575637.16563183687623924422.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251230160730.641868-1-s.ivanov@proxmox.com>

On Tue, 30 Dec 2025 17:06:58 +0100, Stoiko Ivanov wrote:
> as described in the bug-report having a vlan-interface on a physical
> NIC (eno1.1234) as bridge port - allowed users until
> 057f62f ("fix #7118: fix bridge port detection when plugging netdev with vlan")
> 
> to stack 2 802.1q tags on a packet leaving a VM (not quite QinQ, as
> both packets have the TPID of a plain 802.1q tag [0].
> 
> [...]

Applied, thanks!

btw. I think the notion of physical bridge ports turned out to be not such a
great representation of what we actually want here, it mnight make sense to
rename this method–at least on the master branch. An option might be e.g.,
"get_upstream_bridge_ports".

[1/1] fix #7193: allow vlan-interfaces as physical bridge ports
      commit: ca27acb6d430bdd9b2f8b5e854c00e582a13a563


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

      reply	other threads:[~2025-12-31  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 16:06 [pve-devel] " Stoiko Ivanov
2025-12-31  7:11 ` 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=176716506419.2575637.16563183687623924422.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal