PfBlockerNG v2.0 w/DNSBL
-
-Update- Logging worked for about 20 minutes, then stopped. It would actively update on what seemed to be about 30 second intervals. Is there a logging setting that needs to change?
The IP Alerts are taken from the pfSense Firewall Logs. So you can clear the firewall log to start fresh.
For DNSBL the log is taken from /var/log/pfblockerng/dnsbl.log
If you are getting sporatic DNSBL logging, ensure that your LAN device(s) only have pfSense as its DNS server, as any other DNS server settings could be round-robin to other DNS servers and will bypass DNSBL.
Ensure that you can ping the DNSBL VIP, and browse to the DNSBL VIP and get the 1x1 pix.
-
I don't think its a good idea to have your NAS provide DNS resolution for your Network.
You are potentially opening yourself up to security implications by doing this…
Appreciate the input.
The NAS is in a remote location and except for OpenVPN its not open to the world. It
s my backup target and also provides add blocking DNS over OpenVPN that runs on it.You should be able to utilize the pfSense Resolver for your OpenVPN connections (Which will use DNSBL). Just need to set those connections to use pfSense DNS. I am not sure what DNS server is used in your NAS, but you may be opening yourself to cache poisioning and other potential issues.
-
Thanks,
Not sure it belongs in this thread but I should elaborate.
Currently pfS is not in active use except for learning/testing things out.
Attached image shows current setup where the NAS is OVPN server and adblocking DNS server, HOME1-net is with family in another country and HOME2-net is my home, it does not provide DNS for HOME2-net. The Synology DNS server uses bind and provides adblocking DNS for OVPN clients and the HOME1 LAN/WiFi only.you may be opening yourself to cache poisioning and other potential issues.
Curious if that is the case in the current situation, see image, thank you.
You should be able to utilize the pfSense Resolver for your OpenVPN connections (Which will use DNSBL).
Yes, in the new setup pfS will be OVPN/DNS server for HOME2-net, the NAS will become OVPN client for my backup and I thinking about leaving the NAS adblock DNS server for the HOME1-net active, nice for the family.
-
-Update- Logging worked for about 20 minutes, then stopped. It would actively update on what seemed to be about 30 second intervals. Is there a logging setting that needs to change?
The IP Alerts are taken from the pfSense Firewall Logs. So you can clear the firewall log to start fresh.
For DNSBL the log is taken from /var/log/pfblockerng/dnsbl.log
If you are getting sporatic DNSBL logging, ensure that your LAN device(s) only have pfSense as its DNS server, as any other DNS server settings could be round-robin to other DNS servers and will bypass DNSBL.
Ensure that you can ping the DNSBL VIP, and browse to the DNSBL VIP and get the 1x1 pix.
DNS is set correctly as suggested already. Looking at the log from the shell is the same.
-
-Update- Logging worked for about 20 minutes, then stopped. It would actively update on what seemed to be about 30 second intervals. Is there a logging setting that needs to change?
The IP Alerts are taken from the pfSense Firewall Logs. So you can clear the firewall log to start fresh.
Clearing the log only clears everything BUT DNSBL
-
-Update- Logging worked for about 20 minutes, then stopped. It would actively update on what seemed to be about 30 second intervals. Is there a logging setting that needs to change?
Ensure that you can ping the DNSBL VIP, and browse to the DNSBL VIP and get the 1x1 pix.
I can ping the VIP but cannot get the 1x1 pixel
-
The Synology DNS server uses bind
Well atleast its using a decent DNS Server, just ensure that DNSSEC is enabled… I'm always uneasy about these types of devices running the DNS role... Once you put pfSense into the mix, you could then utilize the pfBlockerNG package to get all the additional features it offers.
-
-Update- Logging worked for about 20 minutes, then stopped. It would actively update on what seemed to be about 30 second intervals. Is there a logging setting that needs to change?
Ensure that you can ping the DNSBL VIP, and browse to the DNSBL VIP and get the 1x1 pix.
I can ping the VIP but cannot get the 1x1 pixel
To clear the DNSBL log:
rm /var/log/pfblockerng/dnsbl.log
BY any chance do you have an Anti-virus/Firewall pkg on your desktop that might be causing issues… Seen someone who had Avast doing some 'DNS tunneling' and causing issues with DNSBL. Also check your browser Addons... If your not getting the 1x1, then DNSBL won't work as expected...
-
The only thing I have for AV is MS Security Essentials. Tried turning it off and no changes. The list has cleared and is now staying that way.
-
To clear the DNSBL log:
rm /var/log/pfblockerng/dnsbl.log
BY any chance do you have an Anti-virus/Firewall pkg on your desktop that might be causing issues… Seen someone who had Avast doing some 'DNS tunneling' and causing issues with DNSBL. Also check your browser Addons... If your not getting the 1x1, then DNSBL won't work as expected...
What could possibly be blocking me to the DNSBL VIP?
-
If you are in a multi-segmented Lan network, there is a in the DNSBL tab to auto create a Floating allow rule for the selected Lan networks.
-
If you are in a multi-segmented Lan network, there is a in the DNSBL tab to auto create a Floating allow rule for the selected Lan networks.
That is already checked and created
-
I have added all lists on my apu.
Now my unbound is very slow. It takes more than 800ms to resolve a hostname.
The flicker.conf list is about 60mb.
I have increased some values like Message Cache Size and Number of Hosts to Cache. 50mb and 100000. But it is still so sloooow.
Any ideas?
Thank you -
I have added all lists on my apu.
Now my unbound is very slow. It takes more than 800ms to resolve a hostname.
The flicker.conf list is about 60mb.
I have increased some values like Message Cache Size and Number of Hosts to Cache. 50mb and 100000. But it is still so sloooow.Ensure that your LAN devices can ping the DNSBL VIP, and also that they can browse to the DNSBL VIP and get the 1x1 pix. If any of those two tests fail, you will see slowness as the browser is timing out waiting for the DNS resolution to the blocked Domains.
-
Thats works fine.
I tested the dns resolution time in the Diagnostic menu.
With top I can see that unbound takes a lot of cpu for some time. -
Is the Resolver in "Forwarder" or "Resolver" mode?
What DNS settings are defined in the pfSense General Tab? As these settings are used by the pfSense box itself…
When testing the ping/browse to the DNSBL VIP, do that from the LAN clients and not from pfSense itself.
If you're in a multi-segmented LAN, ensure to use the 'DNSBL Permit Rule' option in the DNSBL Tab. Also clear your Browser/OS cache.
-
Resolver Mode.
No multi segmented LAN.
VIP is tested from remote.
I tested a dns resolution like www.IBM.com on pfsense box.
The slow network is reproducible on many devices.
Maybe there is a mistake in my config which unbound makes that slow.
-
Is the Resolver in "Forwarder" or "Resolver" mode?
What DNS settings are defined in the pfSense General Tab? As these settings are used by the pfSense box itself…
When testing the ping/browse to the DNSBL VIP, do that from the LAN clients and not from pfSense itself.
If you're in a multi-segmented LAN, ensure to use the 'DNSBL Permit Rule' option in the DNSBL Tab. Also clear your Browser/OS cache.
Unfortunately not 100% sure of what fixed it, but the DNSBL alerts are current. On to the next…
-
Ive just noticed an annoying bug when pressing save on the Firewall/pfBlockerNG/Edit/IPv4 page if there are any errors all your data gets wiped out :-(
Can you please leave the data so if can be corrected?
FYI, this bug was fixed by the following pfSense commit for pkg_edit.php:
https://github.com/pfsense/pfsense/commit/a654d899cd5d288501fea1ec52dba2e3f0e479baIts in the pfSense Dev version and will be in the next pfSense 2.3.2 release.
-
pfBlockerNG v2.0 …When a DNS request is made for a domain that is listed in DNSBL, the request is redirected to a Virtual IP address where an instance of Lighttpd Web Server will collect the packet statistics and push a '1x1' GIF image to the Browser…
Just curious why you chose to use lighttpd vs. the nginx webserver that is already built in. Was this for backwards compatibility with older versions?