Messages

Hi,

Good news regarding multicore support. We have released a test binary. Kindly contact the support team via the "Have Feedback" option located in the bottom right corner of the UI if you wish to try it out.

Hi,


The Web tab shows only the http connections. Please check TLS or Connections tab to see https connections as well.

 

Best regards

Hi,

There was a conflict between the Elasticsearch versions in the mimugmail and Zenarmor repositories. However, with the latest update, mimugmail has reverted to version 7. You can opt to use Elasticsearch from the mimugmail repository and configure Zenarmor to use it as a remote database, or you can install Elasticsearch 8 from the Zenarmor repository.

Hi,

The issue might be due to a policy misconfiguration. These applications rely on DNS, and if DNS is encrypted, they cannot block the traffic. Your explanation contradicts Zenarmor and similar tools. Please share a report by following the instructions in the link below.
https://zenarmor.com/docs/support/reporting-bug

 

Hi,

This is not expected, Can you share a report by following the instructions in the below lin

https://zenarmor.com/docs/support/reporting-bug

Hi,

The timeout issue appears to persist. Please go to Settings, navigate to Reporting & Data, select Database, and reset the reporting. Then check again.

Hi @granute,

Thanks for the feedback. I'm going to forward your feedback to the documentation team.


Best regards

Hi,

This is a temporary partition used to store trace logs for device updates and other activities. To identify the largest folder, navigate to the `/usr/local/zenarmor/run/tracefs/{interface_name}` directory and use the command `du -sh *`. Once identified, you can remove the folder if necessary. Zenarmor retains this data for troubleshooting purposes.

Alternatively, you can increase the partition size by going to Settings > Reporting & Data > Database and adjusting the Tracefs Partition Size. It is recommended to set it to 150 MB to adequately store trace data.

Hi,

The multicore support is in developmentstage and we plan to ship it with version 2.1 in July.

Hi,

Can you share a few sample to control their category in Zenarmor DB?

Hi,

OPNsense remove after cron service restart if you add a manuel entry to cron file. To make it permanent in GUI please do the followings

1- create a file in "/usr/local/opnsense/service/conf/actions.d/actions_reportingdb.conf"

2- File content should be
[start]
command:service elasticsearch restart
parameters:
type:script
message:Zenarmor Reporting DB is restarting
description:Zenarmor Reporting DB Restart

3- Navigate System - Settings - Cron

4- Add a new cron, set the time and date settings and select "Zenarmor Reporting DB Restart" in Command field and save the cron.

Hi,

Please check the following github project.

https://github.com/b4b857f6ee/opnsense_grafana_dashboard

Hi,

Use the following command to restart Elasticsearch: service elasticsearch restart.

Hi,

Which database are you using? Could you please share its version?

Hi,

Zenarmor has its own policies and works independently of OPNsense's firewall rules. So, you don't need to recreate or modify your existing OPNsense rules after installing Zenarmor.

For the best setup, we recommend protecting the LAN side with Zenarmor. In this configuration, Zenarmor policies are applied first for outbound traffic, while OPNsense handles inbound traffic.

You can check the following documentation for best practices and policy configuration guidance:

https://www.zenarmor.com/docs/opnsense/policies/configuring-policy
https://www.zenarmor.com/docs/guides/best-practices-for-zenarmor-deployment


Best regards