eBlocker's DHCP service keeps running in expert network mode with external DHCP

[eblosug]

How to reproduce this issue:

• Set up eBlocker VM
• Change network mode to "expert" with external DHCP
• Start Wireshark on client with display filter "dhcp"
• Renew DHCP lease on client
• There will be one DHCP request and two DHCP ACK responses shown in Wireshark

One DHCP response comes from the external DHCP (e.g. the router), the other one from eBlocker's DHCP which is still running.

This issue was observed on an eBlocker VM but not on a Raspberry Pi.

[eblosug]

While building the VM image I forgot to explicitly disable the DHCP service.

The update to eBlockerOS 2.10 contains an update of the DHCP server which enables the service. But it's still not started due to an invalid configuration ("Not configured to listen on any interfaces").

However, if the eBlocker is now configured to use the expert network settings with an external DHCP, the local DHCP configuration is written regardless and as a result the DHCP service is now enabled and running.

[eblosug]

As a workaround:

• If you have console access, disable the service manually: systemctl disable isc-dhcp-server
• Otherwise, go to eBlocker's network settings (expert mode), switch the DHCP service to "eBlocker", reboot and then switch back to "external".