When an interface is configured outside of NetworkManager's knowledge
(like libvirt's or docker's bridge), then NetworkManager generates an
in-memory connection profile and pretends(!) that this is active. This
is to show that something is going on with the device, and
NetworkManager is supposed to
I don't think it's helpful to reopen bugs that were closed for years.
The original issue was identified and confirmed to be fixed.
It's unlikely that the new symptoms have the same cause as the original
one. But even so, it would require information to understand the new
symptoms better.
Let's d
2 matches
Mail list logo
