[Bug 1618522] Re: netplan does not generates .network files just for ethernet

Lukas Märdian 1618522 at bugs.launchpad.net
Wed Mar 16 13:24:43 UTC 2022


Moving it over to the netplan.io project, as nplan is deprecated.

I think we actually have an upstream way of matching Type=ether nowadays
(as of systemd v245+), so we should reconsider implementing a fix for
this.

https://github.com/systemd/systemd/commit/ef62949a23a2d6dc722659cc527f6e0006135dc9

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nplan (Ubuntu)
       Status: Triaged => Invalid

** Tags added: rls-jj-incoming

-- 
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/1618522

Title:
  netplan does not generates .network files just for ethernet

Status in netplan.io package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On my pi3 I have an image with the ubuntu-core snap rev 354 and I get
  the following netplan configuration file after the first boot:

  ubuntu at localhost:~$ cat /etc/netplan/00-initial-config.yaml
  network:
   version: 2
   ethernets:
     all:
      match:
       name: "*"
      dhcp4: true

  This generates the following .networkd file

  ubuntu at localhost:~$ cat /run/systemd/network/10-netplan-all.network
  [Match]
  Name=*

  [Network]
  DHCP=ipv4

  If I look now at the output of networkctl I see it also tries to
  manage my mlan0 device which is a WiFi one and should be managed
  according to the netplan rule:

  ubuntu at localhost:~$ networkctl
  IDX LINK             TYPE               OPERATIONAL SETUP
    1 lo               loopback           carrier     configured
    5 eth1             ether              no-carrier  configuring
    6 eth0             ether              routable    configured
    7 mlan0            wlan               no-carrier  configuring

  In summary, the networkd generator inside netplan currently does not
  limit the generated .network file to tell networkd to only look at
  ethernet devices but rather tell it to control every device available
  on the system.

  Expectation: Specifying a wildcard rule in a netplan configuration
  file for ethernet devices should tell the configured networking system
  to only consider ethernet devices and nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1618522/+subscriptions




More information about the foundations-bugs mailing list