Installation of pfBlockerNG breaks NAT Port Forwading Rules
-
Hello,
I have two pfSense boxes with the same problem. As soon as I install PfBlockerNG and only turn on (to start) Top Spammer blocking and reload, I can no longer control my NAT Port forwarding rules. I have to reload the config back to before pfBlockerNG was installed and can then control NAT rules again. The GUI shows the changes I made; however, when I check the NAT rules in Command Prompt they are not there.
pfBlockerNG: 3.2.0_5
pfSense: 23.05.1-RELEASE (amd64)Is there a known bug? I'm kind of stuck and hoping someone has some insight. Thank you!
-
@jlauzer If you are not inside the USA, you can not activate that list (Top Spammers) without the knowledge, what it actually is...
-
@Bob-Dig I am in the US.
I just did some further testing. I reloaded these boxes back to a working config. I'm able to toggle off and on port forwarding. I then installed pfBlockerNG and reloaded with DNSBL turned on through the setup wizard. Still able to toggle Port forwarding. As soon as I enabled IP and selected Top Spammers (both) and reloaded, toggling any NAT settings broke. (Note, it doesn't matter what list I enable, they all seem to cause the break at reload).. So it seems something in the IP reload is the cause. Identical issue on both appliances that I have at two different locations....
-
@jlauzer said in Installation of pfBlockerNG breaks NAT Port Forwading Rules:
I am in the US.
Ok, then you have to set the Firewall Maximum Table Entries to two million, if you have the RAM.
-
@Bob-Dig It looks like that was the trick! I'm able to toggle the port forwarding rules on and off now. Thank you!!
-
@jlauzer said in Installation of pfBlockerNG breaks NAT Port Forwading Rules:
Thank you!!
You're welcome!
