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 ABD491FF145 for ; Thu, 22 Jan 2026 11:53:31 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BDBAC13716; Thu, 22 Jan 2026 11:53:49 +0100 (CET) Mime-Version: 1.0 Date: Thu, 22 Jan 2026 11:53:46 +0100 Message-Id: To: "Yahya Jabary" X-Mailer: aerc 0.20.0 References: <20260122105010.1968075-1-y.jabary@proxmox.com> In-Reply-To: <20260122105010.1968075-1-y.jabary@proxmox.com> From: "Shannon Sterz" X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1769079168633 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.089 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: Re: [pve-devel] [PATCH docs v1] warn about fail-open default in vlan 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 Cc: 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" 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 > --- > 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