From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Thomas Ellmenreich <t.ellmenreich@proxmox.com>,
pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-docs v2 1/1] network/sdn: update and clean up VLAN information
Date: Tue, 27 Oct 2026 11:33:45 +0100 [thread overview]
Message-ID: <15d56bac-eada-425a-bad8-47fc71a93591@proxmox.com> (raw)
In-Reply-To: <DMAC819IRQO7.3SV0Z7XI2T3F1@proxmox.com>
On 10/21/26 9:28 AM, Thomas Ellmenreich wrote:
> On Tue Oct 20, 2026 at 3:54 PM CEST, Stefan Hanreich wrote:
>> On 10/20/26 8:45 AM, Thomas Ellmenreich wrote:
>
> [snip]
>
>>> +[[vlan_common_issues]]
>>> +Common Issues
>>> +^^^^^^^^^^^^^
>>> +
>>> +.Issue: Configuring VLAN on interface that is member of bridge
>>> +
>>> +It's not recommended to configure a VLAN on an interface that is a member of a
>>> +bridge. Doing so will "blackhole" all traffic of that VLAN on the bridge.
>>
>> Might need a more specific example so this becomes clearer? It's hard to understand
>> otherwise imo.
>
> If I understand correctly, the example [0] you mention further down would be
> an instance of 'blackholing' the traffic. Perhaps I could mention that
> example here instead of creating a separate point for it.
>
> Is this assumption correct?
Yes, although I'm unsure if we should include the concrete examples for the issues,
as it is easy for people to copy-paste them accidentally when not paying attention.
Maybe it'd make more sense to skip the "Configuring VLAN on interface that is member
of bridge" issue altogether as it is rather generic and doesn't really say much and
not an issue per-se. It's imo better to have the concrete failure scenarios in this
section and then tell users how they would identify / rectify it.
e.g. "GW gets lost after reboot" -> "Check if GW is configured on VLAN-aware bridge"
prev parent reply other threads:[~2026-10-27 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 6:45 [PATCH pve-docs v2 1/1] network/sdn: update and clean up VLAN information Thomas Ellmenreich
2026-10-20 9:16 ` Michael Köppl
2026-10-20 13:54 ` Stefan Hanreich
2026-10-21 7:28 ` Thomas Ellmenreich
2026-10-27 10:33 ` Stefan Hanreich [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=15d56bac-eada-425a-bad8-47fc71a93591@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.ellmenreich@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