GNOME Bugzilla – Bug 732998
NM duplicates vmnet* connections whenever interfaces are reconfigured
Last modified: 2020-11-12 14:26:16 UTC
Version: 0.9.10.0 Whenever I restart the vmware service (which reconfigures the vmnet1 and vmnet8 interface), NM adds two new connections for those devices. This looks like this: root@pluto:~# nmcli d | grep vmnet vmnet1 ethernet connected vmnet1 vmnet8 ethernet connected vmnet8 root@pluto:~# nmcli c | grep vmnet vmnet8 25d63e87-b9a0-4545-9920-9e17e4b993ad 802-3-ethernet vmnet8 vmnet1 38260717-216f-471e-965e-0ec75a426f79 802-3-ethernet vmnet1 root@pluto:~# service vmware restart root@pluto:~# nmcli c | grep vmnet vmnet8 501b154e-fd90-4183-b827-4b632ea540f8 802-3-ethernet vmnet8 vmnet1 b5149458-7056-4072-bcea-832efae4a198 802-3-ethernet vmnet1 vmnet8 25d63e87-b9a0-4545-9920-9e17e4b993ad 802-3-ethernet -- vmnet1 38260717-216f-471e-965e-0ec75a426f79 802-3-ethernet -- root@pluto:~# nmcli d | grep vmnet vmnet1 ethernet connected vmnet1 vmnet8 ethernet connected vmnet8 root@pluto:~# service vmware restart root@pluto:~# nmcli d | grep vmnet vmnet1 ethernet connected vmnet1 vmnet8 ethernet connected vmnet8 root@pluto:~# nmcli c | grep vmnet vmnet1 90fef5e0-54b6-4cb4-ac19-ab90cf92484d 802-3-ethernet vmnet1 vmnet8 f6fdb645-e966-4215-8452-a4982f96a816 802-3-ethernet vmnet8 vmnet8 501b154e-fd90-4183-b827-4b632ea540f8 802-3-ethernet -- vmnet1 b5149458-7056-4072-bcea-832efae4a198 802-3-ethernet -- vmnet8 25d63e87-b9a0-4545-9920-9e17e4b993ad 802-3-ethernet -- vmnet1 38260717-216f-471e-965e-0ec75a426f79 802-3-ethernet -- And so on. A debug log is attached. I vaguely remember that we already debugged this but I can't find a corresponding bug report anymore, so I'm filing this new one. Afaicr Dan suspected some issues in the assume functionality.
Created attachment 280392 [details] NM debug log
When NM creates a connection during connection-assumption, it does not delete it afterwards. This will be addressed by bug 731937. Another thing is, that the connection that NM generates does not match to the ones that it generated previously. Looks like the reason is that the generated connection has address-labels, and when a connection has such labels, matching always fails.
Michael, could you please show the generated connections? For example, what does `nmcli connection show uuid UUID` give you (for two different generated connections on one device)
(In reply to comment #3) > Michael, could you please show the generated connections? > > For example, what does `nmcli connection show uuid UUID` give you (for two > different generated connections on one device) and possibly `ip addr` output. Thank you!!
Before the restart: vmnet8 987257ef-1852-4b02-afdb-3f3e2bf4c340 802-3-ethernet vmnet8 vmnet1 e333b4f9-7331-4853-822f-e83f5e603e85 802-3-ethernet vmnet1 connection.id: vmnet1 connection.uuid: e333b4f9-7331-4853-822f-e83f5e603e85 connection.interface-name: vmnet1 connection.type: 802-3-ethernet connection.autoconnect: no connection.timestamp: 1405371126 connection.read-only: no connection.permissions: connection.zone: -- connection.master: -- connection.slave-type: -- connection.secondaries: connection.gateway-ping-timeout: 0 802-3-ethernet.port: -- 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: yes 802-3-ethernet.mac-address: 00:50:56:C0:00:01 802-3-ethernet.cloned-mac-address: -- 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: ipv4.method: manual ipv4.dns: ipv4.dns-search: ipv4.addresses: { ip = 192.168.3.1/24, gw = 0.0.0.0 } ipv4.routes: ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.never-default: no ipv4.may-fail: yes ipv6.method: link-local ipv6.dns: ipv6.dns-search: ipv6.addresses: ipv6.routes: ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.ip6-privacy: -1 (unknown) ipv6.dhcp-hostname: -- GENERAL.NAME: vmnet1 GENERAL.UUID: e333b4f9-7331-4853-822f-e83f5e603e85 GENERAL.DEVICES: vmnet1 GENERAL.STATE: activated GENERAL.DEFAULT: no GENERAL.DEFAULT6: no GENERAL.VPN: no GENERAL.ZONE: -- GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/24 GENERAL.SPEC-OBJECT: -- GENERAL.MASTER-PATH: -- IP4.ADDRESS[1]: ip = 192.168.3.1/24, gw = 0.0.0.0 IP6.ADDRESS[1]: ip = fe80::250:56ff:fec0:1/64, gw = :: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether f0:de:f1:9b:13:b2 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 08:11:96:8d:d4:90 brd ff:ff:ff:ff:ff:ff inet 192.168.178.110/24 brd 192.168.178.255 scope global dynamic wlan0 valid_lft 833877sec preferred_lft 833877sec inet6 fe80::a11:96ff:fe8d:d490/64 scope link valid_lft forever preferred_lft forever 4: wwp0s29u1u4i6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 02:80:37:ec:02:00 brd ff:ff:ff:ff:ff:ff 5: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff 6: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff inet 192.168.3.1/24 brd 192.168.3.255 scope global vmnet1 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 7: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff inet 192.168.4.1/24 brd 192.168.4.255 scope global vmnet8 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever
After restarting vmware: vmnet8 d273022b-0306-4674-b4d2-cada7c42060d 802-3-ethernet vmnet8 vmnet1 63720455-3fa3-4ab2-bf21-7a56d4592249 802-3-ethernet vmnet1 vmnet8 987257ef-1852-4b02-afdb-3f3e2bf4c340 802-3-ethernet -- vmnet1 e333b4f9-7331-4853-822f-e83f5e603e85 802-3-ethernet -- connection.id: vmnet1 connection.uuid: e333b4f9-7331-4853-822f-e83f5e603e85 connection.interface-name: vmnet1 connection.type: 802-3-ethernet connection.autoconnect: no connection.timestamp: 1405371277 connection.read-only: no connection.permissions: connection.zone: -- connection.master: -- connection.slave-type: -- connection.secondaries: connection.gateway-ping-timeout: 0 802-3-ethernet.port: -- 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: yes 802-3-ethernet.mac-address: 00:50:56:C0:00:01 802-3-ethernet.cloned-mac-address: -- 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: ipv4.method: disabled ipv4.dns: ipv4.dns-search: ipv4.addresses: ipv4.routes: ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.never-default: no ipv4.may-fail: yes ipv6.method: ignore ipv6.dns: ipv6.dns-search: ipv6.addresses: ipv6.routes: ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.ip6-privacy: -1 (unknown) ipv6.dhcp-hostname: -- connection.id: vmnet1 connection.uuid: 63720455-3fa3-4ab2-bf21-7a56d4592249 connection.interface-name: vmnet1 connection.type: 802-3-ethernet connection.autoconnect: no connection.timestamp: 1405371279 connection.read-only: no connection.permissions: connection.zone: -- connection.master: -- connection.slave-type: -- connection.secondaries: connection.gateway-ping-timeout: 0 802-3-ethernet.port: -- 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: yes 802-3-ethernet.mac-address: 00:50:56:C0:00:01 802-3-ethernet.cloned-mac-address: -- 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: ipv4.method: manual ipv4.dns: ipv4.dns-search: ipv4.addresses: { ip = 192.168.3.1/24, gw = 0.0.0.0 } ipv4.routes: ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.never-default: no ipv4.may-fail: yes ipv6.method: link-local ipv6.dns: ipv6.dns-search: ipv6.addresses: ipv6.routes: ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.ip6-privacy: -1 (unknown) ipv6.dhcp-hostname: -- GENERAL.NAME: vmnet1 GENERAL.UUID: 63720455-3fa3-4ab2-bf21-7a56d4592249 GENERAL.DEVICES: vmnet1 GENERAL.STATE: activated GENERAL.DEFAULT: no GENERAL.DEFAULT6: no GENERAL.VPN: no GENERAL.ZONE: -- GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/26 GENERAL.SPEC-OBJECT: -- GENERAL.MASTER-PATH: -- IP4.ADDRESS[1]: ip = 192.168.3.1/24, gw = 0.0.0.0 IP6.ADDRESS[1]: ip = fe80::250:56ff:fec0:1/64, gw = :: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether f0:de:f1:9b:13:b2 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 08:11:96:8d:d4:90 brd ff:ff:ff:ff:ff:ff inet 192.168.178.110/24 brd 192.168.178.255 scope global dynamic wlan0 valid_lft 833774sec preferred_lft 833774sec inet6 fe80::a11:96ff:fe8d:d490/64 scope link valid_lft forever preferred_lft forever 4: wwp0s29u1u4i6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 02:80:37:ec:02:00 brd ff:ff:ff:ff:ff:ff 5: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff 8: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff inet 192.168.3.1/24 brd 192.168.3.255 scope global vmnet1 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 9: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff inet 192.168.4.1/24 brd 192.168.4.255 scope global vmnet8 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever
(In reply to comment #6) > 8: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UNKNOWN group default qlen 1000 > link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff > inet 192.168.3.1/24 brd 192.168.3.255 scope global vmnet1 ah, right, I think I know what the problem is; NMSettingIP4Config will only accept labels of the form that ifcfg-rh generates (eth, "eth0:1"), so having labels in other forms must be messing things up. We should fix it so that NMSettingIP4Config, NMIP4Config, and NMPlatform accept any kind of label, and it's only ifcfg-rh that has the $DEVICE:$NUM requirement.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).