From: Stefan Hanreich <s.hanreich@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH] sdn: evpn: allow vlan-aware vnets
Date: Wed, 9 Sep 2026 10:06:02 +0200 [thread overview]
Message-ID: <78ae2a30-c64d-47de-937a-f1cf38f9a9cb@proxmox.com> (raw)
In-Reply-To: <06a5831f0c8de47dc97614be9395940682117d3f.camel@groupe-cyllene.com>
On 9/9/26 6:52 AM, DERUMIER, Alexandre wrote:
> Hi,
>
> they are also another way (that work with vxlan, but I'm not sure with
> evpn),
>
> https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-515/Network-Virtualization/VXLAN-Devices/
> https://blog.vyos.io/evpn-vxlan-enhancements-introducing-single-vxlan-device-support
> https://github.com/FRRouting/frr/pull/12364
>
> it's mapping vlan tags from a vlan aware bridge to vnis, and transport
> them in a single vxlan interface.
>
>
> It was pretty new and buggy 5year ago, so I never tried to implemented
> it,
> maybe it could be interesting to look at it.
Yes, we were discussing this as well in order to implement the VLAN-based
approach - @Gabriel has tested it internally already and it seemed to
work quite well from what he said. For the other approach with VLAN
tags inside the VXLAN packet the current workaround is needed though.
prev parent reply other threads:[~2026-09-09 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 21:49 [PATCH] sdn: evpn: allow vlan-aware vnets Thomas Glanzmann
2026-09-08 9:45 ` Stefan Hanreich
2026-09-08 20:56 ` Thomas Glanzmann
2026-09-09 8:40 ` Stefan Hanreich
2026-09-09 9:22 ` Gabriel Goller
2026-09-09 4:52 ` DERUMIER, Alexandre
2026-09-09 8:06 ` Stefan Hanreich [this message]
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=78ae2a30-c64d-47de-937a-f1cf38f9a9cb@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@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