I had some issues with my system upgrade with Plasma 6 and had to enable an earlier snapshot and then update. All good now except that my VM is no longer working. Here is what I have:-
alastair@HP-Z640-1:~> sudo nmcli connection show
[sudo] password for root:
NAME UUID TYPE DEVICE
Wired connection 1 8fca2d7c-733a-3102-92ae-1cb74cfd7a54 ethernet enp0s20u6
lo a8d5fcb3-7606-4e18-8a8b-23bbaac73ff1 loopback lo
vnet1 08f156c1-8b30-49a6-bfde-812fe96d43ec tun vnet1
USB_Bridge 67da45c2-e203-4eab-b617-76a9f35192e9 bridge br0
USB-connection 4049f9a2-3961-43f3-9e5e-6c33186a5d1b ethernet eno1
alastair@HP-Z640-1:~>
and my network connections:-
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname enp0s25
3: enp0s20u6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 56:fa:5c:7c:10:e3 brd ff:ff:ff:ff:ff:ff
inet 192.168.169.137/24 brd 192.168.169.255 scope global noprefixroute enp0s20u6
valid_lft forever preferred_lft forever
inet6 fe80::21da:3a2f:5770:3448/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 2e:be:ab:85:75:c9 brd ff:ff:ff:ff:ff:ff
6: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:20:88:07 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe20:8807/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
alastair@HP-Z640-1
Two questions; I am missing something and eno1 should be the one which has the static address, not the USB connection.
I thought I had it right but alas no.
here is what I have:
alastair@HP-Z640-1:~> nmcli con show
NAME UUID TYPE DEVICE
bridge-br0 85d984c9-34fb-47b3-b1fc-9e1ccca1b908 bridge br0
Ethernet connection 1 0a5cd829-eac4-42ed-8fd1-94fc69ab6c39 ethernet eno1
Ethernet connection 2 8d745703-1768-45cd-98da-027717334b55 ethernet enp0s20u2
lo 306e89ca-732e-4bb1-bdc7-3cd17f2fc20d loopback lo
bridge-slave-eno1 8f4615f6-2efd-4c9d-98f1-fb026faab056 ethernet --
alastair@HP-Z640-1:~>
and the addresses:-
alastair@HP-Z640-1:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.169.137/25 brd 192.168.169.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::41be:23ad:44a5:86a4/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp0s20u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether c6:d9:f9:9d:74:21 brd ff:ff:ff:ff:ff:ff
inet 192.168.169.229/25 brd 192.168.169.255 scope global dynamic noprefixroute enp0s20u2
valid_lft 84108sec preferred_lft 84108sec
inet6 fe80::44b9:c419:db0f:84b1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 2e:be:ab:85:75:c9 brd ff:ff:ff:ff:ff:ff
alastair@HP-Z640-1:~>
But the slave does not seem to be right and the icon in my task manager has blue circling activity permanently working. It seems the bridge is not being used although I thought I had enabled it with:-
nmcli con add type bridge-slave ifname eno1 master br0
alastair@HP-Z640-1:~> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 70:5a:0f:3a:fa:27 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.169.137/25 brd 192.168.169.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::3306:49e8:d007:9d6a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp0s20u6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
link/ether 56:fa:5c:7c:10:e3 brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 2e:be:ab:85:75:c9 brd ff:ff:ff:ff:ff:ff
inet6 fe80::2cbe:abff:fe85:75c9/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
alastair@HP-Z640-1:~>
arvidjaar had an important point and a reboot solved most of my problems after I had found that if I unplugged the usb dongle and plugged it in again it was given a new address label. Of course half way through the day I had also forgotten to unplug the machine from power to re-set the Intel NIC so that wasted a while!
The plasma 6 installation and all the KDE rubbish that comes with KDE is now making my machine very sluggish indeed, not helped by massive number of emails being connected by imap but it is working and the adventure with Plasma 6 and snapshots has removed all trace of my VPN testing which had been braking my system.
It’s Friday night so I am stopping now. Thanks again for all your help.
Hi arvidjaar,
I went back to your earlier advice on this from when I was moving from Wicked to NM. I didn’t follow, as in understand it all at the time but now I see the point.
Once I had overcome all my errors and mistakes earlier I did find the reboot completed the configuration and all is OK for now.