the problem occurs on 5.0, but should happen on master too.

I have a dhcp client configured before zebra is launched.
dhcp client offers a default route on an interface named mgmt0: 0.0.0.0/0 via 10.0.2.3, mgmt0
then I launch zebra.

at one moment, I release DHCP
what happens is that the default route is unseleted on zebra : * K 0.0.0.0/0 10.0.2.3
whereas on kernel, route is suppressed
ip ro show shows nothing

this leads to inconsistencies, because If I create a static IP address with the same IP mapping, the zebra will consider that kernel route will install, and will prevent other default routes to install.

the attached document depicts 3 cases, with traces

• case dhcp client
• case default route suppressed thanks to iproute2
• case ip address suppressed