Public bug reported:

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.

** Affects: nplan (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  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
+  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
+ 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.

** Description changed:

- On my current pi3 I have with the ubuntu-core snap (rev 354) I get the
- following netplan configuration file:
+ 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.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to