Network Manager is generating wrong profiles

[Karl Weber]

Hi Beniamino!

On Dienstag, 17. Juni 2025 09:48:08 CEST Beniamino Galvani wrote:
> On Mon, Jun 16, 2025 at 12:29:28PM +0200, Karl Weber wrote:
> > Hi,
> > 
> > I observe a strange behaviour of Network Manager and would like to ask, if 
> > this is a bug or a feature. If it is a feature, I would greatly appreciate 
an 
> > explanation about why Network Manager (NW) works the way it does.
> > 
> > On my PC I have two NICs, eth0 and eth1. eth0 is connected to a router and 
> > configured by the router using DHCP. eth1 is connected to the intranet and 
> > configured manually.
> > 
> > For both I have a persistent configuration in files /etc/NetworkManager/
system-
> > connections/ethN.nmconnection for N = 0,1. They are given at the end. 
> > Furthermore, I have a config file /etc/NetworkManager/conf.d/99-
serverlike.conf.
> > 
> > My PC runs openSUSE Leap 15.6 with NM out of the BOX, except for the three 
> > files mentioned.
> > 
> > When I boot this PC, both NICs are configured as expected and working well. 
The 
> > same is true, when I restart NM with systemctl restart NetworkManager.
> > 
> > However, when the PC is suspended and waking up again, thing work 
differently. 
> > 
> > At the beginning, when I did not have the file 99-serverlike.conf at all, 
NW 
> > was generating a new profile for eth1 and using this one. With this new 
> > configuration eth1 was not working at all. The configuration in 
> > eth1.nmconnection was ignored. eth0, on the other hand, was configured as 
> > defined through eth0.nmconnection -- and working.
> 
> Hi,
> 
> what is the name of the new profile generated by NM? 

nmcli con show
NAME                     UUID                                  TYPE      
DEVICE 
eth1                     1128a130-b97f-4c11-ab7f-18ae9d1a8e51  ethernet   eth1   
eth1                     5f258f8a-dc4d-4557-9a7c-6f5f8f88f917  ethernet   eth1   
eth0                     7ba00b1d-8cdd-30da-91ad-bb83ed4f7474  ethernet   eth0   
lo                       ddab96c7-7d75-4efc-a7d7-fa9fc3fe2a2d  loopback   lo   

The fist one is newly created. I cannot find a file for it, so NM seems to have 
it only in its memory. The content is at the end, copied from nmcli con show 
eth1.

> Which version of
> NM? It's not clear to me why this profile is generated. 

Version 1.44.2

> Please run
> "nmcli general logging level trace" as root, reproduce the issue by
> suspending and waking the system, and then attach the relevant logs,
> for example:
> 
>   journalctl -u NetworkManager --since='5 minutes ago'
> 
> Note that the log level change is not persistent and is lost when the
> service (or the system) is restarted.


connection.id:                          eth1
connection.uuid:                        1128a130-b97f-4c11-ab7f-18ae9d1a8e51
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              eth1
connection.autoconnect:                 no
connection.autoconnect-priority:        0
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   0
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
connection.dns-over-tls:                -1 (default)
connection.mptcp-flags:                 0x0 (default)
connection.wait-device-timeout:         -1
connection.wait-activation-delay:       -1
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          no
802-3-ethernet.mac-address:             00:D8:61:2E:33:09
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist:   --
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:        --
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:            --
802-3-ethernet.wake-on-lan:             default
802-3-ethernet.wake-on-lan-password:    --
802-3-ethernet.accept-all-mac-addresses:-1 (default)
ipv4.method:                            disabled
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.routing-rules:                     --
ipv4.replace-local-rule:                -1 (default)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-iaid:                         --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --