PfBlockerNG v2.0 w/DNSBL
-
alexa is a preference thing.
Enabling it means you will not accidentally block popular websites. On the flipside should one of those sites ever get compromised, you also wouldnt be filtering it.
My own reason for posting here is I wonder if anyone has an issue with unbound been unresponsive during reload's? If I add the cryptolocker domains of which there is almost 1 million of them (surely some are dead and not been cleaned up), unbound then needs 20+ seconds to reload at which time it is unresponsive.
-
Hi BBcan177,
Thanks for the awesome package. I had a quick question for you. I added quite a few feeds that you had mentioned in the beginning of this thread and everything was working great. Anyway, I found some more feeds, like really big ones and tried to add those.
It loaded, but the database grew to about 1.4 million entries. Firstly, it started giving me a message about a 2 million hard limit and also, my entire device basically crashed. I have the SG-2440, so it's not one of the higher end models, but I didn't think it would crash the device.
Anyway, Unbound could not be reloaded and it reverted back to the smaller database (which was about 500,000 URLs). Can my device just not handle that big of a table or is there some other way to fix this?
FYI, the two lists that I added that killed the system were these:
http://osint.bambenekconsulting.com/feeds/dga-feed.gz
http://osint.bambenekconsulting.com/feeds/c2-dommasterlist.txtThanks,
AK
My device is higher end than yours, it didnt crash but unbound started been weird, it kept restarting and on each restart it was unresponsive.
I then did a bit of research as I found it very hard to believe that dga list is all live domains and it turns out I am right.
Basically the dga list is someone has inputted known seeds used by botnets and made a list of all the possible domains to be used from those seeds, these are not verified live domains so given the resource complications I removed the dga, the c2 list is verified active domains,. but of course is also much smaller so shouldnt give you problems to use.
-
alexa is a preference thing.
Enabling it means you will not accidentally block popular websites. On the flipside should one of those sites ever get compromised, you also wouldnt be filtering it.
My own reason for posting here is I wonder if anyone has an issue with unbound been unresponsive during reload's? If I add the cryptolocker domains of which there is almost 1 million of them (surely some are dead and not been cleaned up), unbound then needs 20+ seconds to reload at which time it is unresponsive.
Thanks, I will try it and see then wager the results.
-
Still looking for some guidance on this topic? Policy Based Routing to a VPN Gateway results in no pfblockerNG filtering. How can I fix this?
It looks like I got one thing working on my setup but killed DNSBL in the process.
I recently setup policy based routing where my pass firewall rules determine the Gateway to be used. I did this so that I could have one interface route all traffic through my VPN client and another interface not utilize the VPN at all. That works great, but ever since I set that up I have 0 hits on all of my DNSBL feeds and ads are coming through.
Any ideas on how I can use pfBlockerNG DNSBL while still utilizing policy based routing for my purposes?
-
quick update since my post is now out of date as to what is going on with my device.
unbound was not crashing but it was the restarts for the dhcp renewals which I now stopped by patching services.inc, I did enable the DGA list again but as I said before the DGA list is not live domains but a domain list generated from discovered seeds of malware domain generators, of course the domains could be made live at any given moment so its a way to preemt them.
-
I've got everything back up and running again. pfblockerng w/ DNSBL, openvpn client & server.
But now all of my DNS requests go through my ISP. Not really a big deal, but is it possible to make my requests go through google or openvpn dns instead?
I have googe and opendns ip's listed under general setup, and under dhcp. but i keep getting ISP dns.
-
I've got everything back up and running again. pfblockerng w/ DNSBL, openvpn client & server.
But now all of my DNS requests go through my ISP. Not really a big deal, but is it possible to make my requests go through google or openvpn dns instead?
I have googe and opendns ip's listed under general setup, and under dhcp. but i keep getting ISP dns.
In order for DNSBL to block domain name, all clients DNS requests must use the pfSense DNS resolver. https://forum.pfsense.org/index.php?topic=102470.msg572527#msg572527
Normally, in General setup : you leave the DNS servers fields empty, you disable Allow DNS server list to be overridden by DHCP/PPP on WAN
in DHCP / Server you leave the DNS Servers fields empty. -
So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.
Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?
It seems like that should work (not that I'd know) but I don't see why it is necessary that pfbng w/ dnsbl uses an ISP's DNS. If it can filter requests going through the ISP couldn't it do the same with any public DNS?
-
Read again https://forum.pfsense.org/index.php?topic=102470.msg572527#msg572527
about forwarding mode. -
Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).
Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.
-
So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.
All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.
Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?
That what pfSense DNS Resolver forwarding mode is for.
-
Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).
Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.
Check the hosts DNS configuration to see what DNS server they use.
-
All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.
OK, awesome, thank-you. This is what I must be doing wrong. As far as I thought, I am using the DNS resolver (not using forwarded, forwarding mode not turned on, and I've removed all entries in general setup & dhcp for alternative DNS servers).
But whenever I run dnsleaktest.com, I still get my ISP's DNS server?What am I doing wrong? How can I run DNS off of pfsenses internal DNS?
I didn't even know pfsense did this natively, I thought if I wanted to use an internal DNS server then I had to set up and run the whole thing on a real or virtual machine, which I dont know how to do.
-
yup pfsense has a DNS Resolver ;)
So now you have to check your hosts/device DNS configuration.
If they get DNS server configuration from a DHCP server, then configure the DHCP server to send pfsense ip.
@ :
Leave blank to use the system default DNS servers: this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the System / General Setup page.
-
awesome, i got it working as its meant to be, thank you for sticking with my ignorant line of questioning!
One last question, how does the "root server" resolve the DNS lookups? as in what tells my pfsense box the ip address that google.com resolves to?
-
https://en.wikipedia.org/wiki/Domain_Name_System
https://en.wikipedia.org/wiki/Root_name_server -
A PR has been merged for pfBlockerNG. v2.1.1_6
https://github.com/pfsense/FreeBSD-ports/pull/253Fixes:
- EasyList has recently changed the format of the feed. DNSBL parser has been updated.
- Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
- Fix DNSBL Certificate creation for pfSense 2.4
-
A PR has been merged for pfBlockerNG. v2.1.1_6
https://github.com/pfsense/FreeBSD-ports/pull/253Fixes:
- EasyList has recently changed the format of the feed. DNSBL parser has been updated.
- Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
- Fix DNSBL Certificate creation for pfSense 2.4
Hello, thanks for all your work on this. I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
-
I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
Yes. And the point of the report is exactly what?
-
I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
Yes. And the point of the report is exactly what?
Please review the linked image. There are two points :
1. "Package is configured but not (fully) installed" (even after reinstallation)
2. "Newer version available" (without the update option)Regards,
Matt
