Interface goes n/a after forcing an update using pfBlockerNG
-
as the subject says, each time I force an update or made it crontabbes, when dealing with pfBlockerNG rules My DMZ interface goes to a n/a status and everything is unreachable.
THE IP address is there, I just have to click on it and save it without changing anything and things goes back online.
It's annoyng to be honest and I don't know if there is something I am missingI am looking everywhere and it's drving me crazy, The updates are scheduled at night and the morning after i have to "save" the interface everytime since it's always n/a
-
@Belgarioz
Do you see any errors in the pfblockerng.log? Is something being blocked in the Alerts/Reports tab? -
Hello,
I just switched the pfblocker from standard to devel and the problem went away.
Sadly I didn't have time to check the logs :(
