[Bug 1988657] Re: VLAN gets IP address assignment from parent device when using "match macaddress"

[Simon Chopin]

I just tried it on all releases up to Kinetic, they're all affected. I
suspect it's actually a bug in systemd-networkd, as the files generated
in /run/systemd/networkd/ look sane enough:

root at firm-mayfly:~# cat /run/systemd/network/10-netplan-eno1.network 
[Match]
MACAddress=00:16:3e:10:7a:c2
Type=!vlan bond bridge

[Network]
LinkLocalAddressing=ipv6
Address=192.168.2.1/24
VLAN=l2club

root at firm-mayfly:~# cat /run/systemd/network/10-netplan-l2club.netdev 
[NetDev]
Name=l2club
Kind=vlan

[VLAN]
Id=10

root at firm-mayfly:~# cat /run/systemd/network/10-netplan-l2club.network 
[Match]
Name=l2club

[Network]
LinkLocalAddressing=ipv6
Address=10.232.228.16/8
ConfigureWithoutCarrier=yes

There wasn't anything suspicious in the journald logs, either.

** Tags added: rls-kk-incoming

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: netplan
       Status: New => Confirmed

** Changed in: netplan.io (Ubuntu)
       Status: New => Confirmed

** Changed in: systemd (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1988657

Title:
  VLAN gets IP address assignment from parent device when using "match
  macaddress"

Status in netplan:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  System is Ubuntu 18.04 with Netplan 0.99-0ubuntu3~18.04.5(amd64)

  When using the "match macaddress" mechanism to guarantee the
  assignment of the ethernet device name to a particular port, VLANs
  added to that device will not get the the IP addresses assigned to
  them but rather the IP address of the parent ethernet device.

  In the example below from my system, the 'l2club' VLAN would get the
  192.168.2.1 address, along with eno1 receiving it.  The address
  10.232.228.16 was not assigned to anything.  With the "match
  macaddress" section was removed, both interfaces would then get the IP
  addresses that were expected.

  network:
    version: 2
    renderer: networkd
    ethernets:
      eno1:
        match:
          macaddress: 00:24:e8:00:00:00
        addresses:
          - 192.168.2.1/24
    vlans:
      l2club:
        id: 10
        link: eno1
        addresses:
          - 10.232.228.16/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1988657/+subscriptions