Messages

Hi There,

Please submit a ticket via the "Have Feedback" option in the bottom-left corner of the UI. Our sales team will then reach out to you to discuss pricing details.

Hi,

I have informed the sales team, and they will be in touch with you shortly.

Hi,

Can you check the /usr/local/zenarmor/log/active/Periodical.log for these timestamps?

Hi,

Thank you for your valuable feedback. Please note that our updates are not limited to adding or removing apps; we are also continuously enhancing existing applications by updating hostnames and IP addresses. While these specific improvements are not yet included in the release notes, I will share your feedback with the product team to ensure better visibility in the future.

Hi all,

These domains will be examined and recategorized.

Hi all,

Thank you for your patience. A fix for this issue will be included in version 2.7.1.


Best regards

Hi Robert,

To reset the reporting database, navigate to Settings > Reporting & Data > Reporting Database > Reset Reporting. This action will remove all existing index files and automatically recreate them.


Best regards
 

Hi,

Our team is currently investigating the issue and will provide an update shortly.

Hi,

This could be a netmap-related issue. Have you tried running Zenarmor in bypass mode to see if the problem persists? Additionally, what is the current throughput?

Hi,

Thank you for the detials. We got your request as a ticket as well and investigating it. We will get back to you as soon as possible.

Hi,

This value is not a configurable parameter within the engine, so it cannot be modified. Furthermore, DNAT typically does not increase session counts. I recommend investigating whether the traffic is being generated by a specific client and checking that client for any potential anomalies.

Hi,

This issue is triggered during heavy UDP traffic when the client reuses the same source port for new requests. Since Zenarmor maintains UDP state tracking, these duplicate tuple requests initially get blocked due to state collision. However, because the client continuously retries on the same port, the state table clears or re-binds the flow, causing the traffic to pass through anyway.

Hi everyone,

Good news for those experiencing this exact kernel panic on OPNsense 26.7:

The root cause—a race condition in generic_mbuf_dtor() during Netmap generic adapter teardown (generic_netmap_dtor)— officially addressed by the OPNsense core team.

You can track the issue, patch status, and upcoming fixes directly on GitHub here:

👉 https://github.com/opnsense/src/issues/314

Thanks to the OPNsense team!

Hi,

It seems different from QUIC issue. We need to check the config file.

Hi,

Can you share the configuration via "'Have Feedback" option?