Bug #9459
closed
patch pf: silence a runtime warning pfr_update_stats: assertion failed.
0%
Description
I get pf warning spam non-stop
pfr_update_stats: assertion failed.
There is a patch to silence pf warning, add that patch to pfsense:
https://svnweb.freebsd.org/base/stable/12/sys/netpfil/pf/pf_table.c?r1=343289&r2=343288&pathrev=343289
Bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874
Files
Updated by Jim Pingle over 5 years ago
- Category set to Rules / NAT
- Target version set to 2.5.0
- Affected Version set to 2.5.x
- Affected Architecture All added
- Affected Architecture deleted (
)
Updated by rub man over 5 years ago
Update: I was able to stop the warnings by disabling nat reflection.
Possible bug?
Updated by rub man over 5 years ago
So I was able to find another way to keep nat reflection turned on and stop the spam. I changed one of the port forward rules from tcp/udp to separate tcp and udp rules. It fixed the issue. tcp/udp port forward rule might be broken.
Updated by Luiz Souza over 4 years ago
- Status changed from New to Feedback
- Assignee set to Luiz Souza
This fix is already merged to 2.5 sources.
Should not be an issue anymore, please confirm with a newer snapshot.
Updated by Anonymous about 4 years ago
- Status changed from Feedback to Resolved
No response from OP. Assumed fixed
Updated by Gerson Barreiros over 3 years ago
I got same issue and i can confirm that after disabling nat reflection errors are gone.
Enabling it again, after some minutes errors are back.
pfsense 2.5.1
Updated by
Updated by Casper B over 1 year ago
Anonymous wrote in #note-5:
No response from OP. Assumed fixed
Still happening here.. v 22.05
patch is in OP, should be made a system patch in pfsense
Updated by Jens Groh over 1 year ago
Casper B wrote in #note-8:
Anonymous wrote in #note-5:
No response from OP. Assumed fixed
Still happening here.. v 22.05
patch is in OP, should be made a system patch in pfsense
That patch is a patch against the paket filter PF itself, that's nothing you can just "apply" on the fly with a system patch but something that is kernel/sys app level and has to be compiled in, that's why it's not a simple "make it happen" system patch.
Cheers
Updated by Casper B over 1 year ago
I see. Thanks for the info.
Issue still exists so status of this bug shouldn't be 'resolved'..
Updated by Jim Pingle over 1 year ago
Given the age of the original issue this was likely fixed before and then regressed in a later version. Please make a new issue and (if possible) include how you are able to make the error happen again on a current development snapshot.