Public bug reported:
There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4: true
Generates a NM connection in /run/NetworkManager/system-connections:
...
[match]
interface-name=en*;
...
But an NM connection can only match one interface, so if two interfaces
like ens2 and ens3 exist, only one of them will be configured, even
though the netplan configuration is expected to be applied to both.
Solving this might involve generating one NM connection in the netplan
plugin per detected interface.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2012902
Title:
netplan plugin: generated NM config when using globbing will be used
for only one connection
Status in network-manager package in Ubuntu:
New
Bug description:
There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4: true
Generates a NM connection in /run/NetworkManager/system-connections:
...
[match]
interface-name=en*;
...
But an NM connection can only match one interface, so if two
interfaces like ens2 and ens3 exist, only one of them will be
configured, even though the netplan configuration is expected to be
applied to both.
Solving this might involve generating one NM connection in the netplan
plugin per detected interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
