New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firewall Inspect feature shows N/A for most of the rules #3620
Comments
I haven't seen the issue either, some things you could try: Reload ruleset to make sure there are no parsing issues:
(shouldn't generate output) Check the output of the following command (which is the same as our stats use):
The labels (e.g. 57e45e98f405ff38156d7ccef945da92) should match in /tmp/rules.debug where you can find the description (or the other way around). |
it could be rules optimised out so no stats can be gathered in the first place |
The reload of the ruleset didn't helped. The output of the second command shows me values for all my rules.
The WebGUI still shows N/A |
Yeeeehaaa, I've found the issue. :) |
HTML encode -> hash mismatch maybe? |
|
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
Describe the bug
Firewall statistics (Inspect) shows N/A for Evaluations, States, Packets and Bytes for most of the rules. Only the NAT rules show current statistics
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The new 'Inspect' feature should show statistics for each of the firewall rules (as I understand).
Screenshots
Relevant log files
Don't know which log file could help to identify the issue.
Additional context
I've already asked some forum members if they knew the issue or how to solve it. But nobody else seems to have this issue.
Environment
OPNsense 19.7.1 (amd64)
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores)
OnBoard Realtek
2 x Realtek GbE OnBoard LAN chips (10/100/1000 Mbit)
The text was updated successfully, but these errors were encountered: