I am unable to reproduce the issue with a multipass "mpqemubr0"
interface, as described in the bug description. It just modifies the
"ipv4.ignore-auto-routes" setting correctly for me in a clean Jammy LXD
container. So I suppose there might be something else on @RO1's system
that causes side effects. RO1, can you please describe your setup more
closely? Are you using the network-manager-fortisslvpn plugin, for
example?
I can reproduce as outlined in comment #5 by Danilo, though. But I'm not
certain if that's exactly the same issue, or just the same symptom?
IIUC the problem is that for virtual interfaces Netplan uses the
interface name as the "NetdefID", which derives the filename as
/run/NetworkManager/system-connections/netplan-NETDEFID.nmconnection.
So if we have two NM connection profiles that use the same "interface-
name", be it because they are created with the same setting (comment #5)
or because one is modified while another one (potentially external to NM
already exists) Netplan will overwrite one with the other, i.e. both
using the same filename/path. When NM loads the 2nd connection at
runtime, it already has a connection profile with that filename in
memory and therefore complains about the additional one.
IMO the root cause is that NM supports multiple connection profiles per
(virtual) interface, while Netplan tries to merge the configuration of
the same (virtual) interface into a single connection profile. I think
we need to adopt Netplan's "netplan_netdef_get_output_filename()"
function (e.g. making use of NM's "connection.id" property) and also
adopt the "netplan_get_id_from_nm_filepath()" function accordingly.
Ideally, resembling NetworkManager's name-conflict-resolution and
escaping logic as closely as possible.
** Also affects: netplan
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089930
Title:
NetworManager crashes when modifing connection (ipv4.ignore-auto-
routes yes)
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2089930/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
