From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 89C961FF145 for ; Thu, 22 Jan 2026 11:49:56 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4E8D21319D; Thu, 22 Jan 2026 11:50:13 +0100 (CET) From: Yahya Jabary To: pve-devel@lists.proxmox.com Date: Thu, 22 Jan 2026 11:50:10 +0100 Message-ID: <20260122105010.1968075-2-y.jabary@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260122105010.1968075-1-y.jabary@proxmox.com> References: <20260122105010.1968075-1-y.jabary@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.001 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH docs] 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 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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. +==== + * *"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. -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel