Netplan

vxlan: VXLAN setting ends up in wrong section

Bug #2000713 reported by Dr. Jens Harbott on 2022-12-29

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Netplan	Fix Released	Medium	Danilo Egea Gondolfo

Bug Description

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.

Lukas Märdian (slyon) on 2023-01-09

Changed in netplan:
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Danilo Egea Gondolfo (danilogondolfo) wrote on 2023-01-09:

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