Mikrotik creates DHCP Client after every reboot

Hello guys,

recently after the last updates I found that my fail-over doesn’t work. After some troubleshooting it turned out that there is a new DHCP client assigned to Eth1 which I haven’t created (Default DHCP client is disabled). It turned out that I cannot disable it but if It is deleted it just comes back after every reboot.

The current configuration is as follow:

Eth1 - PPoE Client which is my main link (There is also a script which updates the gateway)
Eth2 - Static IP (its the back up link)
Eth3-5 - Bridge (DHCP Server)

I’m using a recursive fail-over.

Something which is very interesting for me is that the newly created DHCP client is assigned to Eth1 but it takes Ip address in the same network as the Eth2 port i.e if Eth 1 is PPoE and Eth2 is
10.10.1.1, the DHCP takes 10.10.1.100.

I found a similar topic where this was pointed as something that mikrotik are aware of however the people were talking about CHR. I had no problems for the past year and a half with this configuration and now suddenly it just destroys my fail over.

Edit: The router is hEX S running 6.46.3

Anyone with solution to this problem?

Interfaces → Detect Internet → set Detect Interface List to none

Great, it seems that this is working, but it completely disables the detect internet feature.