all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Yahya Jabary" <y.jabary@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v1] warn about fail-open default in vlan
Date: Thu, 22 Jan 2026 11:53:46 +0100	[thread overview]
Message-ID: <DFV28WZE1KKO.QLI5XZNP6TOJ@proxmox.com> (raw)
In-Reply-To: <20260122105010.1968075-1-y.jabary@proxmox.com>

hey,
not sure what happened here, but you send the same patch twice in
the same thread. once with a version tag and a longer description and
once without. you may want to check your mail setup :)

On Thu Jan 22, 2026 at 11:50 AM CET, Yahya Jabary wrote:
> fix #4642: improve VLAN documentation
>
> Signed-off-by: Yahya Jabary <y.jabary@proxmox.com>
> ---
>  pve-network.adoc | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/pve-network.adoc b/pve-network.adoc
> index 03524e4..23fd2a3 100644
> --- a/pve-network.adoc
> +++ b/pve-network.adoc
> @@ -614,6 +614,14 @@ which is transparently supported by the Linux bridge.
>  Trunk mode is also possible, but that makes configuration
>  in the guest necessary.
>
> +[WARNING]
> +====
> +If no VLAN tag is specified in the guest configuration, the interface defaults
> +to a VLAN trunk. This allows the guest to access *all* VLANs on the bridge by
> +configuring VLAN tags inside the guest OS. To strictly isolate the guest to a
> +specific VLAN (Access Mode), you must define a VLAN tag in the hardware settings.
> +====
> +

other than that: this reads fine to me!

>  * *"traditional" VLAN on the Linux bridge:*
>  In contrast to the VLAN awareness method, this method is not transparent
>  and creates a VLAN device with associated bridge for each VLAN.



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


  parent reply	other threads:[~2026-01-22 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 10:50 Yahya Jabary
2026-01-22 10:50 ` [pve-devel] [PATCH docs] " Yahya Jabary
2026-01-22 10:53 ` Shannon Sterz [this message]
2026-01-22 12:50 ` [pve-devel] [PATCH docs v1] " Fiona Ebner

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=DFV28WZE1KKO.QLI5XZNP6TOJ@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=y.jabary@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