When I did a fresh installation I selected Network Manager during the installation. Big mistake because I now no longer have the option. Please could I have some help enabling this from Yast. I have downloaded wicked but it does not appear as an option in Yast.
@Budgie2 these is no wicked, is deprecated and gone from Tumbleweed, use nmtui or nmcli or the desktop GUI to configure.
They are just simple text files…
Who am I to blow against the wind!
OK but I shall need some help. I have unplugged the USB network connection altogether.
I have been able to restore a dhcp connection on the on-board nic after unplugging and starting over but I cannot get a static IP to work. Every time I have tried previously I have failed. Now I shall have to leave for a quiet time as I have much work on which to catch up.
Many thanks Malcolm.
@myswtest it is but deprecated and not the default…
Many thanks,
I do not want to do it all again as it takes a day’s work to rebuild. I shall wait until I have a VM running and experiment with this if necessary. Meanwhile I now have one connection working, albeit with dhcp address.
Thanks again,
Alastair.
@Budgie2 run nmtui command then (as your user) and create as required.
Or like me I just use a text file copied to /etc/NetworkManager/system-connections/
For example: eno1-static.nmconnection
[connection]
id=eno1-static
type=ethernet
interface-name=eno1
[ethernet]
auto-negotiate=true
mac-address=48:0F:CF:51:4E:24
wake-on-lan=0
[ipv4]
address1=IPADDRESS/24,GATEWAYIP
dns=xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx;
dns-search=mylocal.domain;
method=manual
[ipv6]
addr-gen-mode=stable-privacy
method=disabled
[proxy]
There are more options in the installer that are “default” which a user might change, which I do.
If Wicked is now deprecated, it should not be an option, or at the very least, there should be a warning about it’s future use which was never shown 
Just suggesting.
.
.
There is no official package available for openSUSE Leap 15.5
FWIW, I’m running wicked 0.6.7.3-150500.3.10.1 normally on 3 Leap 15.5 desktops, from the Update repository.
@myswtest at least it is still there to use, it’s not the default, NM only requires one all encompassing file, perfect for deploying both MicroOS (with combustion) on bare-metal and Vagrant machines. Likewise here with 5 network interfaces on this Tumbleweed box, just drop files in place and done…
Hi Malcolm,
Had a few minutes to return to this and used nmtui but the important issue was disconnecting power to the machine. I had forgotten that I could not readily switch from a Windows dual boot without this disconnection because of the bug in the Intel network card firmware.
With only my on-board NIC connected (USB dongle removed,) and after unplugging and re-plugging and booting I was able change from dhcp to a static IP using nmtui without any issues so all good, but I do have one question; the connection is shown as eno1. I had expected eth0.
I am still rebuilding my system after the TW installation, and am also stuck with installing VM. My VMs that had been backed up from when I had been running Leap 15.4 have been binned.
With the new installation of TW I had expected a virgin setup but when I went to Yast I found that KMV server and KMV tools where greyed out as already installed. Having been admonished by Henk for yet another error on my part I would appreciate help with setting up a second network connection for use with VM.
I have connected the USB dongle and am now using NM which is new to me for VM.
I can create add a new connection and assume this should be a bridge but how do I set the interface name?
What other settings should I use. The usb connection is connected to a port on the switch which is assigned to my private subnet with has dhcp server at the firewall end, the same as the first NIC. I assume the second network connection, ie the bridge should be left as dhcp but would be grateful for advice when you have time.
I have two files for the bridge;
/etc/NetworkManager/system-connections # cat br0\ port\ 1.nmconnection
[connection]
id=br0 port 1
type=ethernet
interface-name=enp8s0
master=br0
slave-type=bridge
[ethernet]
mac-address=88:C9:XX:XX:XX:XX
[bridge-port]
/etc/NetworkManager/system-connections # cat Bridge\ connection\ enp8s0.nmconnection
[connection]
id=Bridge connection enp8s0
type=bridge
interface-name=br0
[ethernet]
[bridge]
[ipv4]
method=disabled
[ipv6]
addr-gen-mode=stable-privacy
method=disabled
[proxy]
You see the new way of interface naming… you can always alias the connection via;
#Set altname to eno1
ip link property add dev eno1 altname eth0
A bridge is a bridge, nothing to do, it’s on the vm where the connection static/dhcp is done
Hi Malcolm
Many thanks. I have not been deflected by the siren call of reviving wicked and will refrain from ranting about why NetworkManager has been capitalised so many thanks for the further clues. Am reading up now.
Still not clear. I have two devices, the built-in nic which has only one port and an USB dongle with another lan port.
What do I build on which device. I cannot even see a name for the USB device which I might be able to enter when creating VM.
I did not have these problems with wicked so it is all new to me and I clearly have not grasped how VMs relate to the rest of the world or even the hard drives.
I have therefore tried to start VM with only one network connection, (USB not plugged in) and accepted the defaults for creating a VM and still I have no VM appearing.
What I am hoping to do is have the VM running and visible. What next?
@Budgie2 you plug the usb device in allocated to br0. In the virtual machine, edit the existing network connection to use a bridge device and set the name to br0 (or what ever you called it…) and device model to e1000.
Hi Malcolm,
I have been making some progress but have some noise which I think was from earlier attempts to start VM. My earlier attempts which worked without any problem has been in Laep 15.4 era with wicked but all new attempts have failed. Here is what I have in my network manager now:-
alastair@HP-Z640-1:~> nmcli
enp0s20u6: connected to usb-connection
"ASIX AX88179"
ethernet (ax88179_178a), 7C:C2:XX:XX:XX:XX, hw, mtu 1500
ip4 default
inet4 192.168.169.243/25
route4 192.168.169.128/25 metric 101
route4 default via 192.168.169.129 metric 101
inet6 fe80::5172:82d7:xxxx:xxxx/64
route6 fe80::/64 metric 1024
lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
eno1: connected to eno1
"Intel I218-LM"
ethernet (e1000e), 70:5A:XX:XX:XX:XX, hw, mtu 1500
inet4 192.168.169.137/25
route4 192.168.169.128/25 metric 102
route4 192.168.169.128/25 via 192.168.169.129 metric 102
route4 default via 192.168.169.129 metric 102
usb-connection: connecting (getting IP configuration) to New bridge connection
"usb-connection"
bridge, AA:58:83:DD:1A:C9, sw, mtu 1500
vnet2: disconnected
"vnet2"
tun, FE:54:00:FE:C3:6C, sw, mtu 1500
vnet3: disconnected
"vnet3"
tun, FE:54:00:51:AF:01, sw, mtu 1500
virbr0: unmanaged
"virbr0"
bridge, 52:54:00:5F:18:C4, sw, mtu 1500
vnet0: unmanaged
"vnet0"
tun, FE:54:00:69:E0:BF, sw, mtu 1500
vnet1: unmanaged
"vnet1"
tun, FE:54:00:35:B2:2F, sw, mtu 1500
DNS configuration:
servers: 192.168.169.129 192.168.1.1
interface: enp0s20u6
servers: 192.168.169.129
interface: eno1
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
alastair@HP-Z640-1:~>
I would like to delete the unwanted vnets tunnels but am not sure what where they come from.
I am asking before I attempt a further VM build. I have no idea where the failed creations have been saved, if anywhere but if you think I should clean up please let me know.
Trying to clarify, I have four files in my system-connections directory:-
[connection]
id=eno1
uuid=1b316f6c-37c5-35f8-b5d1-7fc69d1d5066
type=ethernet
timestamp=1696517614
zone=work
[ethernet]
auto-negotiate=true
[ipv4]
address1=192.168.169.137/25,192.168.169.129
dns=192.168.169.129;
may-fail=false
method=manual
route1=192.168.169.129/25,192.168.169.129
[ipv6]
addr-gen-mode=stable-privacy
method=disabled
[proxy]
alastair@HP-Z640-1:/etc/NetworkManager/system-connections>
My USB Dongle connection:-
alastair@HP-Z640-1:/etc/NetworkManager/system-connections> sudo cat usb-connection.nmconnection
[connection]
id=usb-connection
uuid=913d6a25-fcc3-43ff-ad0e-55367a65d36f
type=ethernet
interface-name=enp0s20u6
timestamp=1696522804
[ethernet]
[ipv4]
dns=192.168.169.129;
may-fail=false
method=auto
[ipv6]
addr-gen-mode=default
method=disabled
[proxy]
alastair@HP-Z640-1:/etc/NetworkManager/system-connections>
A possible stray connection:?
alastair@HP-Z640-1:/etc/NetworkManager/system-connections> sudo cat 'New 802-3-ethernet connection.nmconnection'
[connection]
id=New 802-3-ethernet connection
uuid=eed7f958-1c4a-415e-b630-3c9a91a077b2
type=ethernet
autoconnect=false
master=4019f026-df94-450f-9a84-b758252692b7
slave-type=bridge
[ethernet]
[bridge-port]
alastair@HP-Z640-1:/etc/NetworkManager/system-connections>
And my intended bridge connection:-
alastair@HP-Z640-1:/etc/NetworkManager/system-connections> sudo cat 'New bridge connection.nmconnection'
[connection]
id=New bridge connection
uuid=4019f026-df94-450f-9a84-b758252692b7
type=bridge
interface-name=usb-connection
[ethernet]
[bridge]
[ipv4]
dhcp-client-id=192.168.169.129
may-fail=false
method=auto
[ipv6]
addr-gen-mode=stable-privacy
method=auto
[proxy]
alastair@HP-Z640-1:/etc/NetworkManager/system-connections>
Am I on the right track?
Tried but still failing to get a VM:-
Unable to complete install: 'Unable to add bridge enp0s20u6 port vnet7: Operation not supported'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createvm.py", line 2088, in _do_async_install
installer.start_install(guest, meter=meter)
File "/usr/share/virt-manager/virtinst/install/installer.py", line 737, in start_install
domain = self._create_guest(
^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtinst/install/installer.py", line 679, in _create_guest
domain = self.conn.createXML(initial_xml or final_xml, 0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/libvirt.py", line 4523, in createXML
raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: Unable to add bridge enp0s20u6 port vnet7: Operation not supported
I am having trouble understanding bridge and slaves and how they work. I now have 5 system-connections having tried variations on this. Bottom line is that my last try to creat a VM did not give me any errors but neither did it give me a working VM.
I can edit these lines but Yast does not give me an option to create a master and slave, just a bridge so it is difficult for me to proceed, especially when I am not sure where I am going. For what it’s worth here are my 5 connections:-
HP-Z640-1:/etc/NetworkManager/system-connections # ls -l
total 20
-rw------- 1 root root 208 Oct 5 21:33 Ethernet connection 1.nmconnection
-rw------- 1 root root 239 Oct 5 22:27 New 802-3-ethernet connection.nmconnection
-rw------- 1 root root 215 Oct 5 22:27 New bridge connection.nmconnection
-rw------- 1 root root 346 Oct 5 17:54 eno1.nmconnection
-rw------- 1 root root 256 Oct 5 17:53 usb-connection.nmconnection
HP-Z640-1:/etc/NetworkManager/system-connections # cat "Ethernet connection 1.nmconnection"
[connection]
id=Ethernet connection 1
uuid=4a7ebe05-ea50-491d-9c0d-0ba0c397f322
type=ethernet
interface-name=enp0s20u6
master=2b8097bd-aafc-411b-814c-c1fc20d41e26
slave-type=bridge
[ethernet]
[bridge-port]
HP-Z640-1:/etc/NetworkManager/system-connections # cat "New 802-3-ethernet connection.nmconnection"
[connection]
id=New 802-3-ethernet connection
uuid=aa5c465a-88d0-4489-83df-8b6e40d41ac0
type=ethernet
autoconnect=false
master=924007fe-6676-4a76-862b-32fb893d952e
slave-type=bridge
[ethernet]
mac-address=7C:C2:C6:33:10:D0
[bridge-port]
HP-Z640-1:/etc/NetworkManager/system-connections # cat "New bridge connection.nmconnection"
[connection]
id=New bridge connection
uuid=924007fe-6676-4a76-862b-32fb893d952e
type=bridge
interface-name=br(usb)
[ethernet]
[bridge]
[ipv4]
method=auto
[ipv6]
addr-gen-mode=stable-privacy
method=auto
[proxy]
HP-Z640-1:/etc/NetworkManager/system-connections # cat eno1.nmconnection
[connection]
id=eno1
uuid=1b316f6c-37c5-35f8-b5d1-7fc69d1d5066
type=ethernet
timestamp=1696517614
zone=work
[ethernet]
auto-negotiate=true
[ipv4]
address1=192.168.169.137/25,192.168.169.129
dns=192.168.169.129;
may-fail=false
method=manual
route1=192.168.169.129/25,192.168.169.129
[ipv6]
addr-gen-mode=stable-privacy
method=disabled
[proxy]
HP-Z640-1:/etc/NetworkManager/system-connections # cat usb-connection.nmconnection
[connection]
id=usb-connection
uuid=913d6a25-fcc3-43ff-ad0e-55367a65d36f
type=ethernet
interface-name=enp0s20u6
timestamp=1696522804
[ethernet]
[ipv4]
dns=192.168.169.129;
may-fail=false
method=auto
[ipv6]
addr-gen-mode=default
method=disabled
[proxy]
HP-Z640-1:/etc/NetworkManager/system-connections #
@Budgie2 A cluster they would say 
So as your user run nmtui and delete all except the eno1 one (Ethernet connection 1.nmconnection) I’m guessing.
Rename the eno1 profile one to say MainEthernet so we know it’s eno1.
Plug in the USB connector (no cable) and should see something like;
lsusb | grep Ethernet
Bus 004 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
ip a | grep DOWN
20: enp0s20u4u1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
Plug in the ethernet cable and should see it change from DOWN to UP, open a terminal session and run nmcli
Step 1 - Edit a connection;
Step 2 - Add a connection;
Step 3 - Create a Bridge;
