Trying to get vm working with bridge network

Ask Fedora
1

Hi
Im running F41 and have docker on it and use macvlan interface for some. Im wanting to use home assistant but needs to be a VM as the docker version is limited.
Everything is installed but not working. The vm starts and says no IP and after reading it uses the virbro interface on 192.168.122.0/24 and is not accessable from my network.

Read you need a bridge interface but no matter what doc i follow i end up with the host network down.

I need to keep the same IP for the host and have the existing macvlan interface working for the docker containers. Is there a guide that works or is using the macvtap the way to go from a few posts ive seen.
Any help appreciated

Thanks

2

Shared host bridge works like this:
How to make a Virtual Machine present itself to my home network as if it were another physical computer - #7 by vgaetera

If the issue persists, let’s check your configs.

3

Thanks for the info. So ive done that and now got the following

NAME             UUID                                  TYPE      DEVICE
darklight        6353be41-672c-4d74-bdf3-44e162c4a3bb  wifi      wlo1
virbr0           5c4f23ab-58f4-4eb9-bfdf-f14808f58b32  bridge    virbr0
br-4508e7380d4a  85f7521c-d9e7-4ac5-90ca-4a431ad56089  bridge    br-4508e7380d4a
br-a2b8ae1b4e8b  3b0f5414-6b50-4d25-816d-6521d0987b91  bridge    br-a2b8ae1b4e8b
br-b26469ef4d30  52668e75-67f1-4945-9047-884ae71ed93e  bridge    br-b26469ef4d30
br-cd2b71c6c63d  9347a1aa-d1ef-4b0e-a4b3-e8ffbc3a4e64  bridge    br-cd2b71c6c63d
docker0          3b1a3457-cc6b-44d0-ab7b-fa2bc169c79d  bridge    docker0
lo               11c3337e-e131-453c-a3a7-dfbd56702e08  loopback  lo
macvlan_bridge   cb19d4a3-e105-4d99-a201-81f65d12ceec  macvlan   macvlan_bridge
br-1e774f6c18d6  917d6eb8-fb5e-459e-9741-beebe24bdcd4  bridge    br-1e774f6c18d6
br-df5f38c0cd48  53a27816-0124-4a75-91f0-8356178f5d9b  bridge    br-df5f38c0cd48
br-e4b9a130aa89  df274a0a-55c6-4b84-99bb-d89a3c38bc1e  bridge    br-e4b9a130aa89
br-e674832c83a3  711dc439-76e1-4da6-8b62-1dd7c8884d2f  bridge    br-e674832c83a3

the eth0 has gone and now the server has no wired connection. but the wreless. How do i get it to have its original ip back etc

also running the update vm config after changing it for my vm name i get

error: failed to get domain ‘haos’

Thanks

4

The linked instructions should create 2 connections:

  • bridge using the interface br0.
  • ether using any wired interface as a bridge member.

This does not match the output you posted.

5

Its at the bottom, i missed it on first post

NAME             UUID                                  TYPE      DEVICE
Profile 1        8b7cce2c-a4bd-4c95-9e24-40ecb712b1b4  ethernet  enp88s0
darklight        6353be41-672c-4d74-bdf3-44e162c4a3bb  wifi      wlo1
virbr0           5c4f23ab-58f4-4eb9-bfdf-f14808f58b32  bridge    virbr0
bridge           0c9378fd-0d92-4fd2-a37a-306c9282acb4  bridge    br0
br-4508e7380d4a  85f7521c-d9e7-4ac5-90ca-4a431ad56089  bridge    br-4508e7380d4a
br-a2b8ae1b4e8b  3b0f5414-6b50-4d25-816d-6521d0987b91  bridge    br-a2b8ae1b4e8b
br-b26469ef4d30  52668e75-67f1-4945-9047-884ae71ed93e  bridge    br-b26469ef4d30
br-cd2b71c6c63d  9347a1aa-d1ef-4b0e-a4b3-e8ffbc3a4e64  bridge    br-cd2b71c6c63d
docker0          3b1a3457-cc6b-44d0-ab7b-fa2bc169c79d  bridge    docker0
lo               11c3337e-e131-453c-a3a7-dfbd56702e08  loopback  lo
macvlan_bridge   cb19d4a3-e105-4d99-a201-81f65d12ceec  macvlan   macvlan_bridge
br-1e774f6c18d6  917d6eb8-fb5e-459e-9741-beebe24bdcd4  bridge    br-1e774f6c18d6
br-df5f38c0cd48  53a27816-0124-4a75-91f0-8356178f5d9b  bridge    br-df5f38c0cd48
br-e4b9a130aa89  df274a0a-55c6-4b84-99bb-d89a3c38bc1e  bridge    br-e4b9a130aa89
br-e674832c83a3  711dc439-76e1-4da6-8b62-1dd7c8884d2f  bridge    br-e674832c83a3
ether            f321f9db-c430-4772-9fcd-108aca4cca12  ethernet  --
virbr0           bd1b5083-790b-4751-b80d-cc7d7609f9c3  bridge    --
6 
sudo nmcli connection modify ether ifname enp88s0
sudo nmcli connection up ether
sudo nmcli connection delete "Profile 1"
7

Ok it modifies ok and can delete profile 1 but the middle command fails.

 sudo nmcli connection up ether
Error: Connection activation failed: Unknown error
Hint: use 'journalctl -xe NM_CONNECTION=f321f9db-c430-4772-9fcd-108aca4cca12 + NM_DEVICE=enp88s0' to get more details.

Jul 10 15:21:24 fedora-server NetworkManager[1193]: <info>  [1752157284.2982] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5644] device (enp88s0): Activation: starting connection 'ether' (f321f9db-c430-4772-9fcd-108aca4cca12)
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5644] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5647] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5963] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <warn>  [1752157287.5971] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5973] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5975] device (enp88s0): released from controller device br0
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <warn>  [1752157287.5977] device (enp88s0): Activation: failed for connection 'ether'
Jul 10 15:21:27 fedora-server NetworkManager[1193]: <info>  [1752157287.5980] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')

Still have this after

NAME             UUID                                  TYPE      DEVICE
darklight        6353be41-672c-4d74-bdf3-44e162c4a3bb  wifi      wlo1
virbr0           5c4f23ab-58f4-4eb9-bfdf-f14808f58b32  bridge    virbr0
bridge           0c9378fd-0d92-4fd2-a37a-306c9282acb4  bridge    br0
br-4508e7380d4a  85f7521c-d9e7-4ac5-90ca-4a431ad56089  bridge    br-4508e7380d4a
br-a2b8ae1b4e8b  3b0f5414-6b50-4d25-816d-6521d0987b91  bridge    br-a2b8ae1b4e8b
br-b26469ef4d30  52668e75-67f1-4945-9047-884ae71ed93e  bridge    br-b26469ef4d30
br-cd2b71c6c63d  9347a1aa-d1ef-4b0e-a4b3-e8ffbc3a4e64  bridge    br-cd2b71c6c63d
docker0          3b1a3457-cc6b-44d0-ab7b-fa2bc169c79d  bridge    docker0
lo               11c3337e-e131-453c-a3a7-dfbd56702e08  loopback  lo
macvlan_bridge   cb19d4a3-e105-4d99-a201-81f65d12ceec  macvlan   macvlan_bridge
br-1e774f6c18d6  917d6eb8-fb5e-459e-9741-beebe24bdcd4  bridge    br-1e774f6c18d6
br-df5f38c0cd48  53a27816-0124-4a75-91f0-8356178f5d9b  bridge    br-df5f38c0cd48
br-e4b9a130aa89  df274a0a-55c6-4b84-99bb-d89a3c38bc1e  bridge    br-e4b9a130aa89
br-e674832c83a3  711dc439-76e1-4da6-8b62-1dd7c8884d2f  bridge    br-e674832c83a3
ether            f321f9db-c430-4772-9fcd-108aca4cca12  ethernet  --
virbr0           bd1b5083-790b-4751-b80d-cc7d7609f9c3  bridge    --
8

I suspect there’s some conflict with other connections.
Try to deactivate or delete them before the bridge is properly configured.

9

Hi
I will give it a go. Do i need the virtbr0 as i dont intend on haveinf any isolated guests if any more then this one vm

Thanks for the help so far

10

Hi
So i removed the profile 1 wired connection, the bridge, virbr0 and ether. just left the wireless, br-x connections, docker0 and macvlan interfaces. got the same error at the same place when trying to bring the ether up. not sure what to try next?

11

Try to change the order of activation to rule out the remaining connections.

12

Hi
Same
removed all the new ones and profile 1.
created

sudo nmcli connection add type bridge connection.id bridge ifname br0 bridge.stp no
sudo nmcli connection add type ethernet connection.id eth0 master bridge

then tried to bring up eth0 first but got same message

sudo nmcli connection up eth0

Error: Connection activation failed: Unknown error
Hint: use 'journalctl -xe NM_CONNECTION=25827ecb-851d-4f5a-8b6c-7a5b11fe7228 + NM_DEVICE=enp88s0' to get more details.
13

This looks abnormal, you can collect more detailed logs like this:

journalctl -f -S -1h --no-hostname --no-pager -u NetworkManager.service
14

Hi

Ive recreated the bridge and ethernet and below is that output with the journalctl

sudo nmcli connection add type bridge connection.id bridge ifname br0 bridge.stp no
sudo nmcli connection add type ethernet connection.id ether master bridge
sudo nmcli connection up bridge
sudo nmcli connection up ether
Connection 'bridge' (db55c902-c723-472f-b87a-00a0f0e19281) successfully added.
Connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069) successfully added.
Connection successfully activated (controller waiting for ports) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/38)
Error: Connection activation failed: Unknown error
Hint: use 'journalctl -xe NM_CONNECTION=d78510e1-23cc-4e10-ad40-5d1216f63069 + NM_DEVICE=enp88s0' to get more details.

Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.5970] manager: (br0): new Bridge device (/org/freedesktop/NetworkManager/Devices/29)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.5988] device (br0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.5998] audit: op="connection-add" uuid="db55c902-c723-472f-b87a-00a0f0e19281" name="bridge" pid=1216769 uid=0 result="success"
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6024] device (br0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6029] policy: auto-activating connection 'bridge' (db55c902-c723-472f-b87a-00a0f0e19281)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6033] device (br0): Activation: starting connection 'bridge' (db55c902-c723-472f-b87a-00a0f0e19281)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6034] device (br0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6044] device (br0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6368] device (br0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6404] audit: op="connection-add" uuid="d78510e1-23cc-4e10-ad40-5d1216f63069" name="ether" pid=1216780 uid=0 result="success"
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6405] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6411] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6411] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6415] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6732] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.6740] platform-linux: do-change-link[2]: failure 16 (Device or resource busy)
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.6740] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6745] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6747] device (enp88s0): released from controller device br0
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.6748] device (enp88s0): Activation: failed for connection 'ether'
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6759] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6776] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6779] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6780] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6783] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6860] agent-manager: agent[097a85acb50112e1,:1.1514/nmcli-connect/0]: agent registered
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6865] device (br0): state change: ip-config -> deactivating (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6873] device (br0): disconnecting for new activation request.
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.6873] audit: op="connection-activate" uuid="db55c902-c723-472f-b87a-00a0f0e19281" name="bridge" pid=1216788 uid=0 result="success"
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7103] device (br0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7112] device (br0): Activation: starting connection 'bridge' (db55c902-c723-472f-b87a-00a0f0e19281)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7118] device (enp88s0): state change: config -> deactivating (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7123] device (br0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7140] device (br0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7145] device (enp88s0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7167] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7171] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7172] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7178] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.7765] device (br0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8187] agent-manager: agent[b80d7c5793882e1e,:1.1517/nmcli-connect/0]: agent registered
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8191] device (enp88s0): state change: config -> deactivating (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8193] device (enp88s0): released from controller device br0
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8197] device (enp88s0): disconnecting for new activation request.
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8198] audit: op="connection-activate" uuid="d78510e1-23cc-4e10-ad40-5d1216f63069" name="ether" pid=1216816 uid=0 result="success"
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8205] device (enp88s0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8216] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8220] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8227] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8750] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.8758] platform-linux: do-change-link[2]: failure 16 (Device or resource busy)
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.8758] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8759] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8761] device (enp88s0): released from controller device br0
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.8763] device (enp88s0): Activation: failed for connection 'ether'
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8765] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8775] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8778] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8779] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.8782] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9249] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9256] platform-linux: do-change-link[2]: failure 16 (Device or resource busy)
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9257] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9258] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9260] device (enp88s0): released from controller device br0
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9261] device (enp88s0): Activation: failed for connection 'ether'
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9264] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9276] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9281] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9281] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9285] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9807] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9814] platform-linux: do-change-link[2]: failure 16 (Device or resource busy)
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9814] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9815] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9820] device (enp88s0): released from controller device br0
Jul 14 09:29:29 NetworkManager[1204]: <warn>  [1752481769.9822] device (enp88s0): Activation: failed for connection 'ether'
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9824] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9840] policy: auto-activating connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9844] device (enp88s0): Activation: starting connection 'ether' (d78510e1-23cc-4e10-ad40-5d1216f63069)
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9845] device (enp88s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 14 09:29:29 NetworkManager[1204]: <info>  [1752481769.9850] device (enp88s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 14 09:29:30 NetworkManager[1204]: <info>  [1752481770.0292] device (enp88s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 14 09:29:30 NetworkManager[1204]: <warn>  [1752481770.0298] platform-linux: do-change-link[2]: failure 16 (Device or resource busy)
Jul 14 09:29:30 NetworkManager[1204]: <warn>  [1752481770.0298] device (enp88s0): Activation: connection 'ether' could not be attached as port
Jul 14 09:29:30 NetworkManager[1204]: <info>  [1752481770.0299] device (enp88s0): state change: ip-config -> failed (reason 'unknown', managed-type: 'full')
Jul 14 09:29:30 NetworkManager[1204]: <info>  [1752481770.0301] device (enp88s0): released from controller device br0
Jul 14 09:29:30 NetworkManager[1204]: <warn>  [1752481770.0303] device (enp88s0): Activation: failed for connection 'ether'
Jul 14 09:29:30 NetworkManager[1204]: <info>  [1752481770.0305] device (enp88s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')