From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Cyrus <cyruspy@gmail.com>
Subject: Re: [PVE-User] VLAN to VNI translation
Date: Mon, 17 Mar 2025 09:05:40 +0100 [thread overview]
Message-ID: <b2dc4b38-f1b3-487d-9530-37a3698e2d4f@proxmox.com> (raw)
In-Reply-To: <CAEaLa5F33fWYksgDQyOwGPb9PYaFs9oNPsC1L7XSkDZ7xBBEhw@mail.gmail.com>
Hi!
I've looked at this shortly on one of my test clusters and got a basic
setup running, but didn't get around to further looking into how to
integrate it.
Would it be possible for you to create an entry in Bugzilla [1] for
further discussion?
[1] https://bugzilla.proxmox.com/
On 3/15/25 12:03, Cyrus wrote:
> Hello!,
>
> Before requesting something that might already be there...
>
> Is it possible to translate a VNI to a VLAN towards a VM?.
>
> Use case would be:
>
> 1. Define various VNETs in a EVPN zone (might apply to a VXLAN zone too) as
> currently supported.
> 2. Define an optional VLAN tag for a VNET
> 3. Configure a port facing a VM as trunk (vlan aware?)
> 4. Deliver the VNETs as VLANs to the VM on that port.
>
> I don't want to transport VLAN inside a VNI, I want to deliver VNETs as
> VLAN to a guest which will be handling VLAN tagging/untagging. All the
> transport between PVE VTEPs should be kept as is implemented today (VXLAN).
>
> It would be VNI to VLAN translation or VNI/VLAN stitching + trunking
> towards a VM.
>
> Expectations: adding as many new networks as required to a VM without
> adding a vNICs, with other VMs participating in such VNETs in access mode
> and without touching physical switches (VLAN zone)
>
> Regards.
> Cyrus.
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
_______________________________________________
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:[~2025-03-17 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 11:03 Cyrus
2025-03-16 10:33 ` DERUMIER, Alexandre
2025-03-17 8:05 ` Stefan Hanreich [this message]
2025-03-17 10:11 ` DERUMIER, Alexandre
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=b2dc4b38-f1b3-487d-9530-37a3698e2d4f@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=cyruspy@gmail.com \
--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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal