Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan

[Andrew via pve-devel <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 4928 bytes --]

From: Andrew <andrew@apalrd.net>
To: Stefan Hanreich <s.hanreich@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan
Date: Mon, 31 Mar 2025 14:38:08 +0000
Message-ID: <511405BE-CEF9-4C26-8E75-A4235FC58420@apalrd.net>

Given the delays in ifupdown2 development (the patches for vxlan IPv6 have been sitting un-reviewed for 5 months now, and this is the 3rd patch set in * 5 years * that has tried to fix this issue without being merged), can we continue waiting years for them to fix?

The most recent patch in ifupdown2 does not modify the names of the attributes, so going forward with this patch in PVE and updating pve-network accordingly will not cause rework in pve-network if ifupdown ever releases software. 

Andrew

> On Mar 31, 2025, at 03:22, Stefan Hanreich <s.hanreich@proxmox.com> wrote:
> 
> On 3/31/25 06:45, Andrew wrote:
>> Just noticed I didn’t reply to this before - the patch set in ifupdown2 does not actually address IPv6 local tunnel IPs at all.
> 
> 3.9 itself doesn't, but 3.10 should contain the respective patches
> 




[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel