PfBlockerNG v2.0 w/DNSBL
-
I have found some false positives in the iblocklist lists, for example if you preform a dns lookup to "fractal-design.com" (case builder) it would return 62.116.130.8 that if you search https://www.iblocklist.com/search?string=62.116.130.8 if gives a lot of lists (Malicious, Tracking, etc) can it be outdated?
FPs need to be reported to whomever maintains the blocklist. Or just stop using iBlock lists altogether.
I found idiocy like eicar.org on multiple "malware" blocklists. Sigh. Also, people will happily add entire CDN servers (Amazon, etc.) there. Some people just should get out of the blocklist business, stupidity everywhere.
-
I've been getting a lot of false positives in iblock lists, they seemed like a good blacklist provider. What lists are people using in IP and Hosts?
Thank You all
-
Here is the error:
Dec 9 01:04:36 php: rc.bootup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1449641076] unbound[30851:0] debug: creating udp6 socket :: 53 [1449641076] unbound[30851:0] error: bind: address already in use [1449641076] unbound[30851:0] fatal error: could not open ports'
Maybe it has something to do with IPv6? as the error has a udp6 socket shown.
-
Here is the error:
Dec 9 01:04:36 php: rc.bootup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1449641076] unbound[30851:0] debug: creating udp6 socket :: 53 [1449641076] unbound[30851:0] error: bind: address already in use [1449641076] unbound[30851:0] fatal error: could not open ports'
Maybe it has something to do with IPv6? as the error has a udp6 socket shown.
I changed the LAN IPv6 Configuration Type from Track Interface to none
that solved the unbound crashing ;DAs the WAN DHCP didn't provide DHCP6 IP, the LAN IPv6 ip was:
IPv6 Link Local fe80::1:1
this is probably better not to assign LAN IPV6 ip.
now I get :
IPv6 Link Local fe80::1e7e:e5ff:fe1f:fad5Thanks for opening my noob eyes ;)
-
pfBlockerNG (Bootstrap conversion) has been submitted to the devs.
https://github.com/pfsense/FreeBSD-ports/pull/24
If you guys get a chance, I would recommend testing out the latest pfSense v2.3 snapshot as its expected to go Beta soon along with the packages….
2.3 Testing feedback here:
https://forum.pfsense.org/index.php?board=65.0 -
on the DNSBL FEEDS , below on the page have Custom Block List,
I've added some domains there but I can still access them even they are on the block list .
how is this possible ? -
on the DNSBL FEEDS , below on the page have Custom Block List,
I've added some domains there but I can still access them even they are on the block list .
how is this possible ?When you add to an existing custom list, you need to select the "Update custom list" setting at the bottom of the page. Otherwise the list is only updated as per the Alias frequency setting.
-
I know this has been brought up before but I don't think I've seen a resolution. Is there a way around having the SSL certificate error on some pages with the DNSBL enabled?
-
I know this has been brought up before but I don't think I've seen a resolution. Is there a way around having the SSL certificate error on some pages with the DNSBL enabled?
Can you post the URL(s) that you are having issues with, or send them to me via PM? Also what browser are you using?
-
pfBlockerNG (Bootstrap conversion) has been submitted to the devs.
https://github.com/pfsense/FreeBSD-ports/pull/24
If you guys get a chance, I would recommend testing out the latest pfSense v2.3 snapshot as its expected to go Beta soon along with the packages….
2.3 Testing feedback here:
https://forum.pfsense.org/index.php?board=65.0The pkg was merged last night for pfSense 2.3 … Would appreciate any Feedback. Please post feedback to the 2.3 forum thread.
-
Hi,
Thanks BBcan177 for v 2
I'm testing it, upgrade with no problem.
On DNSBL I use your tutorial list and four custom domains:
facebook.com
youtube.com
terra.com.br
terra.comI get Alerts but not block the sites (1.jpg)
On ipv4 lists I get facebook.com blocked using Whois/AS number. With Whois/Domain name didn't work.
-
Hi heliop100,
In regards to DNSBL, make sure that the LAN devices only use pfSense as its DNS server. You probably also needed to add www.facebook.com etc to your domain list.
Since facebook uses several different IPs, using its AS number would be required instead of just the domain name when using the IP block settings.
-
Ok, I change for www.facebook.com, pt-br.facebook.com, and now are working.
This are on my lab.
If I want to do this on my work network, whit my Domain Controllers/DNS Servers, what are the setup.
Use pfSense as DNS for my devices and forward DNS requests from pfSense to the ADs?Thanks
-
Ok, I change for www.facebook.com, pt-br.facebook.com, and now are working.
This are on my lab.
If I want to do this on my work network, whit my Domain Controllers/DNS Servers, what are the setup.
Use pfSense as DNS for my devices and forward DNS requests from pfSense to the ADs?Thanks
To use DNSBL with an internal DNS server, you should have all the local LAN devices point to your internal DNS server only, then have the internal DNS server point its forwarders to pfSense as its only DNS forwarder… You can also add a firewall rule to reject any other outbound DNS that doesn't originate from your pfSense Box.
-
The browser is IE 11 (this is part of a multi-user environment, I have no choice on this one) and the url was a dropbox folder share. I can't give the exact url but should be pretty easy to replicate.
I know this has been brought up before but I don't think I've seen a resolution. Is there a way around having the SSL certificate error on some pages with the DNSBL enabled?
Can you post the URL(s) that you are having issues with, or send them to me via PM? Also what browser are you using?
-
The browser is IE 11 (this is part of a multi-user environment, I have no choice on this one) and the url was a dropbox folder share. I can't give the exact url but should be pretty easy to replicate.
I know this has been brought up before but I don't think I've seen a resolution. Is there a way around having the SSL certificate error on some pages with the DNSBL enabled?
Can you post the URL(s) that you are having issues with, or send them to me via PM? Also what browser are you using?
You can also suppress the domain that is being blocked when you browse to that Dropbox URL.
-
on the DNSBL FEEDS , below on the page have Custom Block List,
I've added some domains there but I can still access them even they are on the block list .
how is this possible ?When you add to an existing custom list, you need to select the "Update custom list" setting at the bottom of the page. Otherwise the list is only updated as per the Alias frequency setting.
i already did those steps however it didn't works,
even rebooted the firewall. -
on the DNSBL FEEDS , below on the page have Custom Block List,
I've added some domains there but I can still access them even they are on the block list .
how is this possible ?When you add to an existing custom list, you need to select the "Update custom list" setting at the bottom of the page. Otherwise the list is only updated as per the Alias frequency setting.
i already did those steps however it didn't works,
even rebooted the firewall.Add both example.com and www.example.com to the list…
(Change example.com) -
Hey BBcan,
2.0 is working great for me, but I did have to make one tweak after install:
The LightHTTPD config for DNSBL has debug enabled by default. This causes a lot of file write I/O for some reason, and on systems with poor disk performance (like the hypervisor I run PFSense on) it has a nasty side-effect of making the 1x1 image take around 5 seconds to be served.
I monitored the LightHTTPD process and saw lots of write activity to /var/log/pfblockerng/dnsbl_error.log every time a client loaded a blocked url.
I was able to fix the issue by disabling log-condition-handling in the pfb_dnsbl_lighty.conf file ( Modified pfblockerng.inc and restarted )
debug.log-condition-handling = "disable"Did you intend to leave this setting on for release of the package? Or should it be updated default to disable?
-
The LightHTTPD config for DNSBL has debug enabled by default. This causes a lot of file write I/O for some reason, and on systems with poor disk performance (like the hypervisor I run PFSense on) it has a nasty side-effect of making the 1x1 image take around 5 seconds to be served.
I monitored the LightHTTPD process and saw lots of write activity to /var/log/pfblockerng/dnsbl_error.log every time a client loaded a blocked url.
I was able to fix the issue by disabling log-condition-handling in the pfb_dnsbl_lighty.conf file ( Modified pfblockerng.inc and restarted )
debug.log-condition-handling = "disable"Did you intend to leave this setting on for release of the package? Or should it be updated default to disable?
Hi ODVPFS,
The debug.log-condition-handling is used to collect HTTPs alerts. Without that option enabled, HTTPs alerts will still be blocked but without the logging.
When a client makes an HTTPs request to a domain that is in the blocked lists, the Resolver (Unbound) forwards the client to the DNSBL VIP address where the DNSBL Lighttpd web server is listening. The browser tries to make an SSL handshake with Lighttpd, but quickly sees that the certificate doesn't match, and the browser should quickly drop the connection and terminate the browser request. Since it doesn't establish the SSL handshake, the 1x1 gif never gets sent, and there is nothing to log. It sounds counter intuitive being an error log, but this debug error log captures the HTTPs domain which is then logged to the Alerts tab. As stated above, you can disable it, however, you will not get any alerts for HTTPs rejected domains without it…
In regards to your delay in serving the 1x1 image, are you on a single LAN subnet or a multi LAN network? Ensure that you are able to ping and browse to the VIP. The HTTP alerts do not use this Lighttpd error log. For multi-lan segments, there is a checkbox in the DNSBL tab to create a floating rule to allow traffic from other LAN subnets.
Here is a tech link to the Lighttpd error conditional log...
http://blog.lighttpd.net/articles/2006/04/02/log-condition-handling-the-hidden-feature-for-debuging/
