is something wrong with pfBlockerNG?
-
This has happened frequenty in the last 1 month - all of a sudden the domain name's in web browser does not resolve and get errror. When i "disable" pfBlockerNG everything is fine and dandy. It just happened again !
-
@netboy next time, try just restarting unbound/DNS
-
@SteveITS said in is something wrong with pfBlockerNG?:
next time, try just restarting unbound/DNS
I tried and this does not resolve the issue - IMHO pfBlockerNG is defintely broken - i have disabled it
-
@netboy said in is something wrong with pfBlockerNG?:
IMHO pfBlockerNG is defintely broken
Can confirm this is nonsensical.
-
@tinfoilmatt The proof: if i disable pfBlockerNG no issues this "clearly" confirms WITHOUT DOUBT it is broken
-
@netboy Well then it would seem that you've successfully resolved your root issue. Nice work.
-
@netboy Pfblockerng is a complicated system with lots of configuration options, and a combination of those CAN break things, however in most cases its not pfblocker but the user.
Having said that, have you checked for any errors? Does php crash?
Does the update process complete succesfully? -
@netblues My observations (logical) - pfBlockerNG was working perfectly fine "before" update pfsense to 25.07.1-RELEASE (arm64)- After the update i have made "zero" changes to pfBlockerNG - Based on this obervation, i logically conclude the update probably broke something that pfBlockerNG depended on? I maybe wrong but this is my cause and effect conclusions.Can others chime in? Do you have similar problems or observations?
-
@netboy Most probaly a configuration regression.
You really need to dig deeper.
From which pf version did you upgrade?
Have you tried removing and reinstalling pfblockerng?Looking to the moon for craters with naked eye doesn't show the one that the crashed spaceship created.
Use a telescope instead.
FWIW, I see quite a few pfblockerng instances on 25.07.1 running with no (apparent) issues τοο
