pfblockerNG possible bug
-
I have allow WAN firewall rules that I keep at the top of rules on that interface However, when enabling pfblockerNG, those rules go to the top automatically and supersede mine. Which defeats the purpose of my allow rules.
So in pfblockerNG, I changed the rule order from the default to pfSense Pass/Match |pfblocker Pass/Match | pfblocker block/reject | pfsense block/reject.
It seemed to be fine when I first enabled it. However, now when checking my WAN rules, there are probably 200+ duplicate rules.
Seems that when pfblocker is restarting it is creating those rules all over again.
-
@solaris81 Screen shots say a thousand words!
-
Don't really need screenshots to show two hundred plus rules that are all duplicates. I have one pass rule for port forwarding purposes that I keep at the top of every else on the WAN firewall. But after setting that option in pfblockerng, it duplicated that rule hundreds of times. Mostly likely when the service was restarted. It was only over a period of a few days.
I ended up having to delete them all.
-
@solaris81 Hoped I didn't imply you needed to show two hundred rules; however, a screen shot of some of the firewall rules just to show us could help. You may need to wait for BBcan177 to help you.
-
@solaris81 said in pfblockerNG possible bug:
Seems that when pfblocker is restarting it is creating those rules all over again.
Upgrade to pfBlockerNG-devel and see if the issue persists
