Cannot modify network properties

In my initial setup I activated WOL and put 9.9.9.9 in my dns.

I now want to modify that, basically deactivate WOL and change the DNS server, but everytime I try to do it through the GUI or omv-firstaid, I loose the connection and the changes won't apply.

I have to force the reset of the computer and then the changes revert back and I can connect.

This computer has also a wifi card that I've tried to configure as a fallback for this, but trying to configure it also fails.

Any clues?

Zitat von votdev

To me it looks ok. DNS 9.9.9.9 has been set and DHCP has delivered the IP address 192.168.137.246.

What is not working right now? Does name resolution does not work?

Sorry if I didn't explain myself correctly before.

It is working correctly, the problem comes when I try to modify this DNS or deactivate WOL, either via GUI or omv-firstaid. I loose connection and the changes don't apply, I only regain connection (the IP shows again in my network) if I force a reset by disconnecting power.

Zitat von votdev

Maybe you are affected by a systemd bug. See https://www.openmediavault.org/?p=3492

I have checked this but the service is running apparently...

root@openmediavault2:~# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-07-17 10:16:46 CEST; 3h 49min ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 507 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 17801)
     Memory: 4.4M
        CPU: 479ms
     CGroup: /system.slice/systemd-networkd.service
             └─507 /lib/systemd/systemd-networkd

jul 17 11:28:26 openmediavault2 systemd-networkd[507]: vethb063b8a: Link UP
jul 17 11:28:27 openmediavault2 systemd-networkd[507]: vethb063b8a: Gained carrier
jul 17 11:28:28 openmediavault2 systemd-networkd[507]: vethb063b8a: Gained IPv6LL
jul 17 12:58:04 openmediavault2 systemd-networkd[507]: veth6132ac5: Link UP
jul 17 12:58:05 openmediavault2 systemd-networkd[507]: veth6132ac5: Gained carrier
jul 17 12:58:06 openmediavault2 systemd-networkd[507]: veth6132ac5: Gained IPv6LL
jul 17 12:58:07 openmediavault2 systemd-networkd[507]: veth6132ac5: Lost carrier
jul 17 12:58:07 openmediavault2 systemd-networkd[507]: veth6132ac5: Link DOWN
jul 17 12:58:07 openmediavault2 systemd-networkd[507]: rtnl: received neighbor for link '42' we don't know about, ignoring.
jul 17 12:58:07 openmediavault2 systemd-networkd[507]: rtnl: received neighbor for link '42' we don't know about, ignoring.

Zitat von votdev

That does not mean you are not affected. The symtoms you describe are matching the problem described in the link. You may apply the changes via UI and then check the status of the service unit. You may also run journalctl -f while applying the changes in the UI. You will surely see that there is some error when getting the IP address via DHCP. To make it short, the OMV project can not do anything here.

So I'm guessing that if instead of using DHCP I configure a static IP the configuration should apply without problems?

Zitat von votdev

Yes

Well it didn't. I configured a static DHCP, still got disconnected and had to force reset.

There were some updates yesterday between which one was for the ethernet card. After this update I'm able to set a static IP and commit the changes, so apparently my error was a mix between this issue and the driver.