When my pc returns from sleep I see a warning about limited networking connectivity. It is probably related to a network bridge I created to have a QEMU macos VM share the network and so have macos File Sharing work. Since I am not a network savvy I followed steps shown on github related to creating that macos VM. (macOS-Simple-KVM/guide-networking.md at master · foxlet/macOS-Simple-KVM · GitHub) Below I have copied the relevant journald log and below that the Networkmanager nmcli recipe I used (which does work). It seems to me that this bridge setup leaves the system in a not so good state. I am ofcourse happy to provide more info.
02-08-2022 13:11 kded5 "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
02-08-2022 13:11 kdeconnectd "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
02-08-2022 13:11 kded5 "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/1”"
02-08-2022 13:11 kdeconnectd "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/1”"
02-08-2022 13:11 NetworkManager <info> [1659438682.2489] manager: NetworkManager state is now CONNECTED_SITE
02-08-2022 13:11 NetworkManager <info> [1659438694.5177] device (br1): carrier: link connected
02-08-2022 13:11 NetworkManager <info> [1659438696.2939] manager: NetworkManager state is now CONNECTED_GLOBAL
02-08-2022 13:22 kwin_x11 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 25564, resource id: 41943773, major code: 18 (ChangeProperty), minor code: 0
02-08-2022 13:22 kwin_x11 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 27023, resource id: 73400340, major code: 18 (ChangeProperty), minor code: 0
02-08-2022 13:24 kwin_x11 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 37022, resource id: 77594808, major code: 2 (ChangeWindowAttributes), minor code: 0
The recipe is:
You can use NetworkManager to control the bridge and tun/tap interfaces, by creating them with the following commands. Replace DEVICENAME with your ethernet card’s device name. (And that is eno1).
Make the Bridge
nmcli connection add type bridge \
ifname br1 con-name mybridge
Attach Bridge to Ethernet
nmcli connection add type bridge-slave \
ifname DEVICENAME con-name mynetwork master br1
Make the Tun/Tap
nmcli connection add type tun \
ifname tap0 con-name mytap \
mode tap owner 1000
NB The “owner 1000” is in the recipe "owner ‘id -u’ " which created an error.
Attach Tun/Tap to Bridge
nmcli connection mod mytap connection.slave-type bridge \
connection.master br1
Attach Bridge to QEMU
Once you have set up the bridge and tun/tap on the host, you’ll have to add the following line to basic.sh (in , replacing -netdev user,id=net0. Change tap0 to your corresponding device name.
-netdev tap,id=net0,ifname=tap0,script=no,downscript=no \
❯ nmcli connection show
NAME UUID TYPE DEVICE
mybridge fec3d3ef-935a-4e64-8ead-85d3bc80231e bridge br1
eno1 8da4fb47-be32-40cf-8f9e-2944bc363124 ethernet eno1
mytap 39e52158-4886-4d31-806e-d4ff654578ed tun tap0
mynetwork d21e4903-4bc8-49e8-b65a-3beb309e247c ethernet --
mybridge and mytap lines are in bright green, the eno1 line is dark green, the mynetwork line is white.