Wrong dev in routing table in case of bridge on vlan

[Matthias Nagl]

network:
    version: 2
    renderer: networkd
    ethernets:
        eno1:
            dhcp4: no
            dhcp6: no
            accept-ra: false
    vlans:
        voffice:
            id: 10
            link: eno1
            accept-ra: false
    bridges:
        broffice:
            interfaces: [ voffice ]
            addresses: [10.200.10.2/24, 10.200.10.3/24 ]
            gateway4: 10.200.10.1
            nameservers:
                addresses: [ "10.200.10.1" ]
            routes:
              - to: 0.0.0.0/0
                via: 10.200.10.1
                table: 10
            routing-policy:
              - from: 10.200.10.0/24
                priority: 10
                table: 10

has the following result:

# ip route list table 10
default via 10.200.10.1 dev broffice proto static
10.200.10.0/24 dev voffice scope link src 10.200.10.2

The intended result would be:

# ip route list table 10
default via 10.200.10.1 dev broffice proto static
10.200.10.0/24 dev broffice scope link src 10.200.10.2

[Mathieu Trudel-Lapierre (cyphermox)]

That's odd. Let's dig in deeper, as it quite likely might be a systemd bug, but I rather be certain it's not us doing something wrong.

Could you please attach the config files generated in /run/systemd/network/ so we can confirm that the routes are created for the right devices?

Thanks!

[Launchpad Janitor (janitor)]

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for netplan because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]