netplan plugin: generated NM config when using globbing will be used for only one connection
Bug #2012902 reported by
Alfonso Sanchez-Beato
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Triaged
|
Medium
|
Unassigned | ||
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
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:
dhcp4: true
Generates a NM connection in /run/NetworkMan
...
[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.
tags: | added: netplan-everywhere |
Changed in netplan: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: foundations-todo |
To post a comment you must log in.