PfBlockerNG v2.0 w/DNSBL
-
However the suppression only seems to happen when you do a force reload, not when you click on the suppress icon
Check your pfBlockerNGSuppress alias and remove all of the single /32 addresses in 50.31.164.x and just use a single /24
-
Hello all, I have my rules now allowing and not blocking, as we should do, I just have one question. Should I add a default reject all to the end of my LAN interfaces? Since I only allow, the traffic that does not match my allow rules will be blocked by default by pfsense, making my browser (for example) wait for a timeout (for example blocked IP's). If I add a reject all to the end of my rules, the request on the browser will be a lot faster, returning a rejected error.
Thank you all
-
Thank you so much for the great tools, it works great so far two weeks now no complains.
i have a request, can we use the DNSBL to block Microsoft Telemtry ? -
http://someonewhocares.org/hosts/
search near the bottom. There might be more lists out there.
-
Thank you so much for the great tools, it works great so far two weeks now no complains.
i have a request, can we use the DNSBL to block Microsoft Telemtry ?https://raw.githubusercontent.com/WindowsLies/BlockWindows/master/hostslist
Taken from project - https://github.com/WindowsLies/BlockWindows -
Thank you so much for the great tools, it works great so far two weeks now no complains.
i have a request, can we use the DNSBL to block Microsoft Telemtry ?https://raw.githubusercontent.com/WindowsLies/BlockWindows/master/hostslist
Taken from project - https://github.com/WindowsLies/BlockWindowsthose are domains, I have plenty of them :)
can those be blocked using DNSBL ? -
-
Is-it normal that during boot, Resolver start twice?
Configuring WAN interface...done. Configuring LAN interface...Starting DNS Resolver...done. Starting DHCPv6 service...done. done. Configuring CARP settings...done. Configuring OpenVPN settings...done. Configuring firewall......done. Starting PFLOG...done. Setting up gateway monitors...done. Synchronizing user settings...done. Starting webConfigurator...done. Configuring CRON...done Starting DNS resolver...done. Starting NTP time client....done. Starting DCHP service....done. Starting DHCPv6 service...done. Configuring firewall......done.
and when I access the Webconfigurator, resolver and ntp are both stopped.
I added Unbound under Service Watchdog and unbound start within 5 min of bootup.
Strange output from starting pfBlockerNG :
Starting package pfBlockerNG... ?done.
-
-
Hey all!
This is just what the doctor ordered! Thans BBcan177, great job!
I have a dumb question. I was looking over the default settings and had a question about the below. If you're going to protect against spam, wouldn't you select "Inbound" as the default instead of "Outbound"? I want to prevent stuff from coming in to the network. I know I'm missing something here, just don't know what it is.
DNSBL IP Firewall Rule Settings:
Select Deny outbound or as per your requirements
select Enable loggingThanks!
-
All connections are initiated from inside to outside direction, so, you should block what starts the connection. Unless you have open ports from the internet to your network.
-
Thanks for the replyl Hugovsky. But I'm still confused.
My mail server is inside my network and is clean. It would seem to me you'd want to block what is coming in from the outside to the ports opened on the mail server, etc.
Sorry, I can be dense at times.
-
Best way to do that is to make an alias and use it with the nat rule that forwards to your server. Remember: the firewall is already blocking everything you don't allow.
-
-
I added Unbound under Service Watchdog and unbound start within 5 min of bootup.
Don't use Service Watchdog with DNSBL as that will interfere with how DNSBL updates.
-
I tried to find out why unbound dies silently on bootup
I did a fresh install, disabling all package before saving the config, bring the config back, normal pkg installation went smoothly.
I enabled all packages except pfBlockerNG and DNSBL , rebooted 2-3 times and unbound is present on reboot.
I enabled pfBlockerNG, DNSBL, on first reboot unbound was alive
After 2-3 reboot it kept dying on reboot.
Watching the services status, I could see it running until DNSBL start, then it dies.
I went thru the /var/log files, no error is logged !Once it is started it keeps running fine.
So I only put unbound in Service Watchdog, not DNSBL, is this ok?
Now unbound restart 1 or 2 minutes after it dies. -
No don't use Service Watchguard for either.
Do you have any of the Unbound DHCP registration checkboxes enabled? If so, disable those.
-
No don't use Service Watchguard for either.
So how do I find out what's making it dies on reboot ?
-
Do you have any of the Unbound DHCP registration checkboxes enabled? If so, disable those.
Nope only Enable DNSSEC Support is ticked.
Network interface is set to ALL
Outgoing interface is set to WANI do have Host Overrides for a local domain (not the local domain of pfense), including the WAN IP of the firewal (it is behind my present pfsense box)
-
Increase the Unbound log verbosity and see if it shows any further details.