From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] [Extern] - Re: Mapping of VLAN tags to Linux bridges: Is that possible?
Date: Mon, 22 Jul 2024 21:27:28 +0200 [thread overview]
Message-ID: <b43f9654-1edc-4709-8dc2-733e6ad02999@dkfz-heidelberg.de> (raw)
In-Reply-To: <mailman.628.1721675915.331.pve-user@lists.proxmox.com>
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
next prev parent reply other threads:[~2024-07-22 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aee1ef2-47f5-4d1c-8600-88cd796be6e7@dkfz-heidelberg.de>
2024-07-22 19:18 ` [PVE-User] " Bastian Sebode via pve-user
2024-07-22 19:23 ` David der Nederlanden | ITTY via pve-user
2024-07-22 19:27 ` Gilberto Ferreira
2024-07-22 19:28 ` [PVE-User] [Extern] - " Frank Thommen
2024-07-22 19:27 ` Frank Thommen [this message]
2024-07-23 11:14 ` Stefan Radman via pve-user
[not found] ` <7de79cbf-90d0-40e2-87ec-dde2f6b21f0c@email.android.com>
2024-07-22 19:28 ` [PVE-User] " Bastian Sebode via pve-user
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=b43f9654-1edc-4709-8dc2-733e6ad02999@dkfz-heidelberg.de \
--to=f.thommen@dkfz-heidelberg.de \
--cc=pve-user@lists.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