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

[Stefan Hanreich]

On 10/9/24 23:05, DERUMIER, Alexandre wrote:
> but we need to be able to not diverge too much from upstream,
> if one day (ok that's waiting since 4 years...) an official
> support is added by cumulus/nvidia.
> (to be honest, the upstream is a lot less active since nvidia have buy
> cumulus/mellanox)
> 
> That's mean maintain both syntax, or plan a config update,
> between 2 majors pve releases. Not a big deal.

yes, it seems a bit tricky, since we'd have to predict what ifupdown2 is
doing - but with the current speed of ifupdown2 development, I'm not
sure if VXLAN IPv6 support will land anytime soon. There's a similar PR
open though in the ifupdown2 github [1].

Since there is currently discussion about moving away from ifupdown2 on
debian-devel [2] [3] and the point of contention is not really about IF
they will be moving away from ifupdown2 but rather WHAT the replacement
will be, we could support our implementation (with possible
compatibility patches) while we move to a new network stack.

> BTW, I don't have followed the ifupdown-ng project since a long time.
> (just follow the early days). Is the project really active and have
> almost same features than ifupdown2 ?  (netlink support, reload support
> with diff of running config,...)

Judging from the current discussion on debian-devel, ifupdown-ng doesn't
seem to be a candidate for the Debian network stack moving forward.
There's some heated discussion between netplan and systemd-networkd,
with some (from my perception) preference for systemd-networkd so we'll
be monitoring that closely for our trixie release.


I'll test this series a bit this week and report back. Would you be
interested in sending a v2 afterwards? (particularly wrt to the perl
style issues). Otherwise I can also take this patch series over. in any
case, have you signed a CLA with us already? Otherwise we cannot include
your patches in our repositories.

[1] https://github.com/CumulusNetworks/ifupdown2/pull/315
[2] https://lists.debian.org/debian-devel/2024/07/msg00098.html
[3] https://lists.debian.org/debian-devel/2024/09/msg00240.html