From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-user-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id D9B5F1FF16E
	for <inbox@lore.proxmox.com>; Mon, 17 Mar 2025 09:05:59 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id E3A22345F8;
	Mon, 17 Mar 2025 09:05:43 +0100 (CET)
Message-ID: <b2dc4b38-f1b3-487d-9530-37a3698e2d4f@proxmox.com>
Date: Mon, 17 Mar 2025 09:05:40 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
 Cyrus <cyruspy@gmail.com>
References: <CAEaLa5F33fWYksgDQyOwGPb9PYaFs9oNPsC1L7XSkDZ7xBBEhw@mail.gmail.com>
Content-Language: en-US
From: Stefan Hanreich <s.hanreich@proxmox.com>
In-Reply-To: <CAEaLa5F33fWYksgDQyOwGPb9PYaFs9oNPsC1L7XSkDZ7xBBEhw@mail.gmail.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.678 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_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
 http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
 information. [proxmox.com]
Subject: Re: [PVE-User] VLAN to VNI translation
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-user-bounces@lists.proxmox.com
Sender: "pve-user" <pve-user-bounces@lists.proxmox.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