Ubuntu
systemd package

netplan does not generates .network files just for ethernet

Bug #1618522 reported by Simon Fels on 2016-08-30

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	netplan.io (Ubuntu)	Triaged	Low	Unassigned
	systemd (Ubuntu)	Won't Fix	Low	Unassigned

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@localhost:~$ cat /etc/netplan/00-initial-config.yaml
network:
version: 2
ethernets:
   all:
    match:
     name: "*"
    dhcp4: true

This generates the following .networkd file

ubuntu@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@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.

See original description

Tags:

Simon Fels (morphis) on 2016-08-30

description:	updated
description:	updated

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-08-30:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nplan (Ubuntu):
status:	New → Confirmed

Martin Pitt (pitti) on 2016-08-30

Changed in nplan (Ubuntu):
status:	Confirmed → In Progress
importance:	Undecided → Medium
assignee:	nobody → Martin Pitt (pitti)

Martin Pitt (pitti) on 2016-09-01

Changed in nplan (Ubuntu):
milestone:	none → ubuntu-16.09

Revision history for this message

Martin Pitt (pitti) wrote on 2016-09-01:

non-working patch Edit (18.8 KiB, text/plain)

This is unfortunately really hairy. networkd, NM etc. have "Type=" fields, which more or less match on the DEVTYPE uevent property. This is properly set for wifis, but it's empty for actual ethernets and also for vlans, some wifi devices, etc. So while I can set the restriction for "wifis:", the attached patch does not actually work as the device type is never actually "ether" (or similar).

So I'm afraid this is currently unfixable at the netplan/networkd/NM level and we need to work around this by replacing the matching of "*" to "en*".

Changed in nplan (Ubuntu):
status:	In Progress → Triaged
assignee:	Martin Pitt (pitti) → nobody
milestone:	ubuntu-16.09 → none

Ubuntu Foundations Team Bug Bot (crichton) on 2016-09-01

tags:

added: patch

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2016-09-01:

Ugggh. Can we at least think about what would be involved in fixing this in the kernel or wherever so it's not a problem forever?

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2016-09-01:

I proposed https://github.com/snapcore/snapd/pull/1830 to work around this.

Revision history for this message

Martin Pitt (pitti) wrote on 2016-09-02:

One way to improve that in userspace would be to at least allow a way to match on "no devtype" in networkd. You cannot currently say Type="" or similar.

Lennart Poettering> hmm, for networkctl we patch that to make this more useful to look at
Lennart Poettering> shouldn'we just do the same in networkd
Lennart Poettering> i.e. accept our fate?
Lennart Poettering> i am pretty sure "networkctl" should show in the Type column precisely the types you can [Match] on, no?
Tom Gundersen> yeah, i guess we can just do that

Changed in systemd (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2016-09-05:

That makes sense I guess. It seems networkctl prints "Type: ether" for things that have DEVTYPE=bridge, just to make things more confusing?

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2017-03-07:

This is somewhat related to https://github.com/systemd/systemd/issues/3998.

For now, there's still no way to do this in systemd; it will require an upstream fix.

Revision history for this message

Dan Streetman (ddstreet) wrote on 2021-06-30:

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status:	Triaged → Won't Fix

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2021-06-30:

The attachment "non-working patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Revision history for this message

Lukas Märdian (slyon) wrote on 2022-03-16:

#10

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

Changed in netplan.io (Ubuntu):
status:	New → Triaged
importance:	Undecided → Medium
Changed in nplan (Ubuntu):
status:	Triaged → Invalid
tags:	added: rls-jj-incoming