Zenarmor Incorrect Device count and detection

Started by pradip.marathon, October 21, 2024, 11:56:45 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions
October 21, 2024, 11:56:45 AM
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?
October 21, 2024, 12:51:05 PM #1
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?
October 21, 2024, 01:36:16 PM #2
How are your TAGs set in the deployment menu in ZA?

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD
October 22, 2024, 07:55:57 AM #3
Quote from: IHK on October 21, 2024, 12:51:05 PM
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.
October 22, 2024, 07:56:41 AM #4
Quote from: Seimus on October 21, 2024, 01:36:16 PM
How are your TAGs set in the deployment menu in ZA?

Regards,
S.

Can you please explain this in details?
October 22, 2024, 09:15:23 AM #5
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).
In theory there is no difference between theory and practice. In practice there is.
October 22, 2024, 12:14:58 PM #6
Quote from: pradip.marathon on October 22, 2024, 07:56:41 AM
Quote from: Seimus on October 21, 2024, 01:36:16 PM
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.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD
October 22, 2024, 12:29:05 PM #7
Quote from: Seimus on October 22, 2024, 12:14:58 PM
Quote from: pradip.marathon on October 22, 2024, 07:56:41 AM
Quote from: Seimus on October 21, 2024, 01:36:16 PM
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.
October 22, 2024, 12:38:34 PM #8
Quote from: dinguz on October 22, 2024, 09:15:23 AM
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
October 24, 2024, 01:07:00 PM #9
Version 1.18 has been released, lets see whether it fixes the issue reported. I will keep you posted.
October 27, 2024, 08:47:41 AM #10
Hi,

Do you face the same issue with 1.18?
Print
Go Up Pages1
User actions