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 8F9DA1FF2AE for ; Mon, 22 Jul 2024 21:49:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B0F7438DA9; Mon, 22 Jul 2024 21:50:06 +0200 (CEST) Message-ID: Date: Mon, 22 Jul 2024 21:27:28 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: pve-user@lists.proxmox.com References: <6aee1ef2-47f5-4d1c-8600-88cd796be6e7@dkfz-heidelberg.de> From: Frank Thommen Organization: DKFZ Heidelberg, Omics IT and Data Management Core Facility (ODCF) In-Reply-To: X-SPAM-LEVEL: Spam detection results: 0 AWL -0.207 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 RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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-User] [Extern] - Re: Mapping of VLAN tags to Linux bridges: Is that possible? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Hi Bastian, maybe I am missing the point: Where is the VLAN tag in your example? Is it encapsulated in the bond name "bond0.90' being for VLAN 90? Frank On 22.07.24 21:18, Bastian Sebode via pve-user wrote: > Hello Frank, > > you can achieve that with normal Linux networking already, without the > need of SDN. > > Over the Network Tab of the Hosts GUI (interface names are examples): > > - Create the Bond/LAG/Port Channel/Trunk on the switch, put the needed > VLANs tagged on it > - Create a "Linux Bond" `bond0` with the host interfaces `ens18 ens19`, > preferably with LACP on Host and Switch. No IP address necessary > - Create a "Linux VLAN" `bond0.90` with the "vlan raw device" `bond0`. > No IP address necessary > - Create a "Linux Bridge" `vmbr90` with the slave interface `bond0.90`. > No IP address necessary, only if you want to manage the server over it > - Attach the VMs to the VLAN bridge > - Repeat for every VLAN you need > > There is also the possibility to have the VLAN Tags on the Linux bridge, > but I would always prefer the mentioned above. > > Hope this helps and others can confirm that the are using such a setup. > > Peace > Bastian _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user