@publictoiletbowl
Hi,
New or not, why not posting in the pfBlokcerng forum ?
615b2328-d87a-4904-a3b7-e3d8c21918a8-image.png
and have a look at the already present posts, as there is a lot to know.
Btw : the DNSBL part of pfBlokcerng has 'nothing' to do with the 'firewall'.
@publictoiletbowl said in new to pfblocker:
Can't assign requested address for 127.0.0.1 port 953
It means that 'some one' ( a process ) is al ready listening on this port 953.
This is most probably another instance of unbound that is acting as a zombie in memory, blocking resources like ports (files, memory etc).
Do this ;
In the GUI, stop the unbound process.
Enter the console (better : use SSH), go for option 8.
Enter
sockstat | grep :953
if this lists one or more lines : you found the process that blocks port 953 !
Example :
unbound unbound 53871 13 tcp4 127.0.0.1:953 *:*
Your mission : kill it (kill them).
Like
kill 53871
where 53871 is the process ID.
If there was more then one : kill them all.
Now, in the GUI, start unbound.
Do a full reload for pfBlockerng.