http://bugzilla.suse.com/show_bug.cgi?id=1106993
http://bugzilla.suse.com/show_bug.cgi?id=1106993#c2
--- Comment #2 from Martin Wilck ---
Workaround: if I bring the "enp0s31f6" connection down manually, NM
auto-connects its configured connection "wired_dhcp" via the same interface
(instead of 'enp0s31f6').
mwilck@apollon:~> nmcli con down enp0s31f6
mwilck@apollon:~> nmcli -a con up suse_de
Connection successfully activated (D-Bus active path:
/org/freedesktop/NetworkManager/ActiveConnection/7)
mwilck@apollon:~> nmcli con
NAME UUID TYPE DEVICE
suse_de 061fd5ed-d901-4553-99be-36fd1551c46f vpn
enp0s31f6
tun0 be945e78-3b59-41ce-b45f-a4e8956669ee tun tun0
virbr0 b52b3c60-0a1a-4571-8601-6a02e276f12b bridge virbr0
virbr1 c9ae8c17-6325-4d5f-9b38-6165971217ee bridge virbr1
vlan10 1e983a59-cc9d-41c8-bd7d-114f965e4c6e vlan vlan10
vlan20 b714ed6e-37fe-4bdc-90ec-06445c508377 vlan vlan20
wired_dhcp b99bd77c-b92a-453d-a714-fef71dfd5586 ethernet
enp0s31f6
...
(compare this to the "nmcli con" output in comment 0).
--
You are receiving this mail because:
You are on the CC list for the bug.