Zebra routing table doesn't clear

[baakie]

Hello everybody,

I have a backup 4G WAN connection and it gets a new dynamic ip address via DHCP every 24 hours like clockwork.
The 4G modem is connected via ethernet to ix3 on a 5100.
pfSense gets the external ip address from my mobile provider, which is nice and what I want.
Furthermore: I use FRR for OSPF dynamic routing only for the networks behind VTI ipsec VPNs.

New the issue:
The old /24 nets from the 4G connection stay visible in the zebra routing table. It's like it doesn't clear them when the DHCP is renewed.
These networks don't appear in the system or OSPF routing table.
Perhaps this is only cosmetic but I already have 12 networks in there because the system has been up for 12 days.
Is this normal? Does it hurt? Can it be reseloved?

Here is a portion of the Zebra routes:

C>* 178.225.41.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.225.244.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.226.41.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.226.44.0/24 [0/1] is directly connected, ix3, 16:23:28
C>* 178.226.105.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.226.248.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.227.101.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.229.218.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.229.251.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.230.36.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.230.249.0/24 [0/1] is directly connected, ix3, 16:23:34
C>* 178.231.48.0/24 [0/1] is directly connected, ix3, 16:23:34