But the memory remains, or never change from static IP to DAIP?

[Thomas_Eichelbu]

Hello Folks, 

an interesting discover ...
we have bunch of Quantum Sparks running somewhere, some with static IP, some with DAIP.
in general its all fine no complains.

but on some Quantum Spark i needed to change the WAN interface from a statically configured IP  to a DAIP object.

two issues struck me:
when changing an existing static IP GW (Quantum Spark) to DAIP it changes its IP to this funny 0.0.0.X IP´s. of course it causes me collisions because of already existig DAIP´s with the same 0.0.0.X. IP´s 
there is this SK for it sk181834
i changed the colliding IP`s in GuiDBedit to different available IP´s all good.

secondly, i saw in GUIDEBIT this only IP´s never really got removed. they still there even when the Interface is set to DAIP.
also this only IP matches in Smartlog, even when it shouldnt,




yes i could easily delete this old IP ...
but is this safe?
also this GW in question is quite unstable regarding VPN ... it comes and goes, and mostly only a reboot helps. sure latest firmware installed!
who has encountered similar scenarios?

[_Val_]

Why this way and not just removing and redefining the GW object from scratch?

[Thomas_Eichelbu]

Hello Val, 

well yes, that´s a valid approach, but you know, this GW objects are used in many many rules and so on ...

just clicking DAIP in the GW properties and tweaking the topology a bit is alot faster 🙂

iam more interested in just removing the IP leftovers stored in GUIDBEDIT, or do i mess up something?