pfBlockerNG update to 3.1.0_3
-
I noticed with the recent update this morning to pfBlockerNG 3.1.0_3 that after install, unbound had to be manually restarted. I hadn't noticed that with updates 3.1.0_1 and 3.1.0_2.
I know this has been an issue in the past with updates to pfBlockerNG but thought it had finally been fixed, but maybe it has reappeared.
Just an observation and is not a big deal as far as I am concerned and as always, THANKS for all the hard work that goes into maintaining this package.
-
This update is not pushed on the 2.5.2 and leaves us with no option than to update to 2.6.0 which kills VLAN's and MultiWAN.
What to do?
-
@jdeloach Hi Unbound restarted just fine for me( I did not have to restart manually) after I updated to 3.1.0_3
-
@uglybrian
Thanks.
Maybe I was too impatient or there is something peculiar about my system. I don't consider it an issue but I know some folks have complained about it in the past. -
@jdeloach said in pfBlockerNG update to 3.1.0_3:
Maybe I was too impatient or there is something peculiar about my system. I don't consider it an issue but I know some folks have complained about it in the past.
Same here, never did it on its own.
-
Updated to 3.1.0_4 a couples of minutes ago, and as usual I forgot to look at the state of unbound, and it was stopped of course.
But, what I do now is doing a full reload, as I see the yellow thingy :
and that will also take care of the unbound issue.
