| 2016-08-30 15:37:23 |
Simon Fels |
bug |
|
|
added bug |
| 2016-08-30 15:38:57 |
Simon Fels |
description |
On my current pi3 I have with the ubuntu-core snap (rev 354) I get the following netplan configuration file:
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. |
On my current pi3 I have with the ubuntu-core snap (rev 354) I get the following netplan configuration file:
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. |
|
| 2016-08-30 15:39:43 |
Simon Fels |
description |
On my current pi3 I have with the ubuntu-core snap (rev 354) I get the following netplan configuration file:
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. |
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. |
|
| 2016-08-30 15:48:53 |
Launchpad Janitor |
nplan (Ubuntu): status |
New |
Confirmed |
|
| 2016-08-30 15:49:35 |
Tony Espy |
bug |
|
|
added subscriber Tony Espy |
| 2016-08-30 16:11:50 |
Martin Pitt |
nplan (Ubuntu): status |
Confirmed |
In Progress |
|
| 2016-08-30 16:11:52 |
Martin Pitt |
nplan (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-08-30 16:11:53 |
Martin Pitt |
nplan (Ubuntu): assignee |
|
Martin Pitt (pitti) |
|
| 2016-09-01 10:26:13 |
Martin Pitt |
nplan (Ubuntu): milestone |
|
ubuntu-16.09 |
|
| 2016-09-01 12:44:24 |
Yann Sionneau |
bug |
|
|
added subscriber Yann Sionneau |
| 2016-09-01 13:59:15 |
Martin Pitt |
attachment added |
|
non-working patch https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1618522/+attachment/4732285/+files/0001-networkd-Restrict-matches-to-definition-s-device-typ.patch |
|
| 2016-09-01 13:59:26 |
Martin Pitt |
nplan (Ubuntu): status |
In Progress |
Triaged |
|
| 2016-09-01 13:59:29 |
Martin Pitt |
nplan (Ubuntu): assignee |
Martin Pitt (pitti) |
|
|
| 2016-09-01 13:59:34 |
Martin Pitt |
nplan (Ubuntu): milestone |
ubuntu-16.09 |
|
|
| 2016-09-01 16:41:13 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2016-09-02 07:37:44 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu) |
|
| 2016-09-02 07:39:31 |
Martin Pitt |
systemd (Ubuntu): importance |
Undecided |
Low |
|
| 2016-09-02 07:39:31 |
Martin Pitt |
systemd (Ubuntu): status |
New |
Triaged |
|
| 2016-09-05 04:07:07 |
Chen-Han Hsiao (Stanley) |
bug |
|
|
added subscriber Chen-Han Hsiao (Stanley) |
| 2016-09-05 22:59:30 |
Michael Hudson-Doyle |
bug |
|
|
added subscriber Michael Hudson-Doyle |
| 2017-03-07 22:43:16 |
Mathieu Trudel-Lapierre |
bug watch added |
|
https://github.com/systemd/systemd/issues/3998 |
|
| 2021-06-30 19:54:23 |
Dan Streetman |
systemd (Ubuntu): status |
Triaged |
Won't Fix |
|
| 2021-06-30 20:27:20 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2022-03-16 13:23:44 |
Lukas Märdian |
bug task added |
|
netplan.io (Ubuntu) |
|
| 2022-03-16 13:23:49 |
Lukas Märdian |
netplan.io (Ubuntu): status |
New |
Triaged |
|
| 2022-03-16 13:23:51 |
Lukas Märdian |
netplan.io (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-03-16 13:23:54 |
Lukas Märdian |
nplan (Ubuntu): status |
Triaged |
Invalid |
|
| 2022-03-16 13:25:58 |
Lukas Märdian |
tags |
patch |
patch rls-jj-incoming |
|
| 2022-03-17 15:18:45 |
Brian Murray |
tags |
patch rls-jj-incoming |
patch rls-kk-incoming |
|
| 2022-05-12 15:12:58 |
Brian Murray |
tags |
patch rls-kk-incoming |
patch |
|
| 2022-05-12 15:13:03 |
Lukas Märdian |
bug task deleted |
nplan (Ubuntu) |
|
|
| 2022-05-12 15:13:48 |
Lukas Märdian |
netplan.io (Ubuntu): importance |
Medium |
Low |
|
