vxlan: VXLAN setting ends up in wrong section

[Dr. Jens Harbott]

If a vxlan is linked to a bridge that has additional data like static routes, the "VXLAN=" tag ends up at the end of the .network file in the "[Route]" section instead of the "[Network]" section where it belongs. The code generating it https://github.com/canonical/netplan/blob/main/src/networkd.c#L949-L961 should be moved to L874 so it is executed before any other sections get created.

[Danilo Egea Gondolfo (danilogondolfo)]

Hi, thank you for your bug report.

I will investigate this further.

Reproducer:

network:
  renderer: networkd
  ethernets:
    eth0:
      routes:
        - to: 10.20.30.40/32
          via: 10.20.30.1
  tunnels:
    vxlan1:
      mode: vxlan
      id: 1
      link: eth0

Result:

[Match]
Name=eth0

[Network]
LinkLocalAddressing=ipv6

[Route]
Destination=10.20.30.40/32
Gateway=10.20.30.1
VXLAN=vxlan1

Result without the route:

[Match]
Name=eth0

[Network]
LinkLocalAddressing=ipv6
VXLAN=vxlan1

[Danilo Egea Gondolfo (danilogondolfo)]

PR addressing this issue https://github.com/canonical/netplan/pull/310

[Pavel Malyshev (afunix)]

When the fix will reach Ubuntu 22.04 LTS?
It's been almost 3 months since "fix committed" and 22.04 is still affected by this.

[Dr. Jens Harbott (j-harbott)]

I guess https://bugs.launchpad.net/netplan/+bug/2025519 is relevant regarding backporting

[Lukas Märdian (slyon)]

It's been released to Jammy, as of https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-7ubuntu0.22.04.2