topic Re: But the memory remains, or never change from static IP to DAIP? in Spark Firewall (SMB)

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

Thomas_Eichelbu — Fri, 08 Nov 2024 11:20:24 GMT

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?

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

_Val_ — Fri, 08 Nov 2024 11:28:08 GMT

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

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

Thomas_Eichelbu — Fri, 08 Nov 2024 11:39:20 GMT

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?

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

PhoneBoy — Fri, 08 Nov 2024 16:49:45 GMT

Anytime you're messing around in (gui)dbedit, you're doing so at your own risk. 🙂
Are you wanting to remove the IP in the "ipaddr" field in the object?

In any case, it's probably safer to create a new object.

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

Thomas_Eichelbu — Mon, 11 Nov 2024 14:31:53 GMT

Hello,

Well yes messing around is of course not what i wanted.
But from a user perspective this is not a deterministic behavior.
If i set an gateway object from static IP to DAIP i must expect that this object is really removing all its static components.
Dealing with this leftovers is creating a random behavior ...

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

PhoneBoy — Mon, 11 Nov 2024 20:39:21 GMT

I assume the fact it's not removing the static components is a bug and should probably be addressed through TAC.