DHCP release, renew WAN ip address after physical link goes down

Hello
I’m using a CCR2004 RouterOS 7.15.1

sfp28-2 is the only physical interface member of bridge called “WAN”.
Interface WAN has dhcp-client configured
I see no dhcp discover after sfp28-2 is restored. → down → up
Why is the dhcp-client lease of interface WAN not flushed when interface sfp28-2 goes down and dhcp discover to be sent after it goes up?
Is this the desired behavior of RouterOS / CRR2004

If so, I would be happy about a script tracking physical port down event to do a dhcp-client release and on up event do a dhcp-discover.
I don’t want to do netwatch and send ping towards target IP.

Thanks a lot

The bridge do not go down if a single port on the bridge is down.

This IS the desired behavior of RouterOS from all the other users.

Then use netwatch to launch the “release” command and renew does it itself when the DHCP server reply again.

Thanks for your input.

Ok, so even though last member of the bridge “WAN” goes down, the IP address of bridge “WAN” stays up.
This is a behaviour I was not aware.

I reconfigured and deleted this bridge.
IP address dhcp-client is now configured under physical port sfp28-2.
It works like a charm. Whenever this port goes down, the IP lease got’s removed properly.