From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] VLAN to VNI translation
Date: Sun, 16 Mar 2025 10:33:56 +0000 [thread overview]
Message-ID: <bb1f008a5582a97548e3e87b7421676ce1591aa8.camel@groupe-cyllene.com> (raw)
In-Reply-To: <CAEaLa5F33fWYksgDQyOwGPb9PYaFs9oNPsC1L7XSkDZ7xBBEhw@mail.gmail.com>
It's not implemented currently, (1vxlan tunnel, with vlan->vni
mapping), because AFAIK it's still buggy with evpn && frr.
(the implementation exist, I have seen a lot of bug report)
https://docs.frrouting.org/en/latest/zebra.html#single-vxlan-device-support
I'll try to re-evaluate it for pve9
-------- Message initial --------
De: Cyrus <cyruspy@gmail.com>
Répondre à: Proxmox VE user list <pve-user@lists.proxmox.com>
À: Proxmox VE user list <pve-user@lists.proxmox.com>
Objet: [PVE-User] VLAN to VNI translation
Date: 15/03/2025 12:03:36
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://antiphishing.vadesecure.com/v4?f=MDk0SW9xRkhTVGYydkJlTIW3tbT6fr
3wO2olQ9DvtVnIC88l_b535xnQ2-t7iy40j6r2uq1a-
CdCqXFVrfJr5w&i=ZURHSDhnY0huQ2tPS3VZahJdhRaQu1ItpJrYkl8wXrA&k=q1N6&r=Rj
IyR1RobkVxVWlHTXhKT3Iz2JLb2iJ83zY8BuwqBM8RdGY4uHVD-
7F03xyDQtHpzE9nazLbPgxy0VoDLSdJwA&s=4d44c9a8a125b8dae76e8d7d37f3a01a001
1ffd8cdd2a59ef83295a06956997d&u=https%3A%2F%2Flists.proxmox.com%2Fcgi-
bin%2Fmailman%2Flistinfo%2Fpve-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-16 10:49 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 [this message]
2025-03-17 8:05 ` Stefan Hanreich
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=bb1f008a5582a97548e3e87b7421676ce1591aa8.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal