Zenarmor Incorrect Device count and detection

[pradip.marathon]

Zenarmor is detecting WAN/public IP addresses in the devices and counting them towards the total device count, which ultimately impacts the licensing count. Could you please provide a solution for this issue?

[IHK]

Quick question; Could you set the "Deployment mode" to Passive (Report Only) mode in the Zenarmor Firewall configuration menu or enable the WAN interface from the Interface menu, even if it's just for testing?

[Seimus]

How are your TAGs set in the deployment menu in ZA?

Regards,
S.

[pradip.marathon]

Quick question; Could you set the "Deployment mode" to Passive (Report Only) mode in the Zenarmor Firewall configuration menu or enable the WAN interface from the Interface menu, even if it's just for testing?

My policies will not work if we set the "Deployment mode" to Passive (Report Only) mode. There is no point of this testing.

[pradip.marathon]

How are your TAGs set in the deployment menu in ZA?

Regards,
S.

Can you please explain this in details?

[dinguz]

Maybe it's better to submit a call with their support department so they can investigate more thoroughly because they have access to your log files and such. I submitted a similar issue and I'm currently running the 1.18 beta which has fixes for this, as well as for the same devices being recognized multiple times with different IP addresses due to DHCP (both private range and 169.254.x.x).

[Seimus]

How are your TAGs set in the deployment menu in ZA?

Regards,
S.

Can you please explain this in details?

Go to ZenArmor > Configuration > Please choose interfaces to protect

And make screenshot of that whole section.

Regards,
S.

[pradip.marathon]

How are your TAGs set in the deployment menu in ZA?

Regards,
S.

Can you please explain this in details?

Go to ZenArmor > Configuration > Please choose interfaces to protect

And make screenshot of that whole section.

Regards,
S.

I have TAG only LAN interface as of now.

[pradip.marathon]

Maybe it's better to submit a call with their support department so they can investigate more thoroughly because they have access to your log files and such. I submitted a similar issue and I'm currently running the 1.18 beta which has fixes for this, as well as for the same devices being recognized multiple times with different IP addresses due to DHCP (both private range and 169.254.x.x).

Yes, submitted with support team already, As per them it will get fixed in upcoming release of 1.18

[pradip.marathon]

Version 1.18 has been released, lets see whether it fixes the issue reported. I will keep you posted.

[sy]

Hi,

Do you face the same issue with 1.18?