[Bug 1738058] Re: vlan usage requires an intermediate step

Dan Streetman 1738058 at bugs.launchpad.net
Wed Jun 30 20:37:36 UTC 2021


please reopen if this is still an issue

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1738058

Title:
  vlan usage requires an intermediate step

Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  If I try to apply vlans directly:

  
  network:
    version: 2
    renderer: networkd
    ethernets:
      eth0: {}
    vlans:
      vlan1:
        id: 1
        link: eth0
        addresses: [ 192.168.0.10/23 ]
      vlan10:
        id: 10
        link: eth0
        addresses: [ 10.0.0.5/24 ]

  The vlan devices never come up, they are left in degraded state by
  networkd. If I define an address for eth0, then eth0 and all of the
  vlans will have the same address. Needless to say, this doesn't work.

  If I use an intermediary device instead, such as a bond:

  network:
    version: 2
    renderer: networkd
    ethernets:
      eth0: {}
    bonds:
      vmaster:
        interfaces: [ eth0 ]
    vlans:
      vlan1:
        id: 1
        link: vmaster
        addresses: [ 192.168.0.10/23 ]
      vlan10:
        id: 10
        link: vmaster
        addresses: [ 10.0.0.5/24 ]

  Then the vlans are correctly applied and brought up by systemd.

  I think this is either a systemd bug or a netplan bug; it's possible
  we don't generate the config quite in the way that systemd expects it
  (even though it looks straightforward enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1738058/+subscriptions



More information about the foundations-bugs mailing list