DNS Blacklist, New Package! Check it out.
-
Does it have any effect when in that order???
-
The order for the Rules does not matter.
-
i like the idea of a block list built into pfsense, but i don't like the idea of a pfsense blocklist, if you could just create the interface so that you can make your own lists that would be great.
thanks.
- have not tried the package yet..
-
The next release will contain the ability to create your own black/white-list within the web configuration.
We will also have the ability to let users upload their own compiled blacklists into the script, or use the one prebuilt with the application.
-
Hi,
I am new to PfSense, I tried using DNS Blacklist and tried to block, Adult Porn and Online Gaming but I beleive it blocks all sites, if I try accessing any site it redirects to Google. For eg I tried indiatimes.com; yahoo.co; rediff.com and our Company website but it all gets redirected to Google, not sure if I am going wrong somewhere or do I need to work on the scripts. -
Highlighted in RED.
The order for the Rules does not matter.
Unless something has changed drastically, the order is critical as pfsense rules are evaluated from the top down. The first rule in your example would match, and pfsense will handle the packet accordingly. I'm not trying to pick on you, but that's a major nuance of pfsense and m0n0wall.
On a completely different note, when I use the DNS Blacklist with the Adult category selected, www.pandora.com is blocked, even though it is not in the domain list for the adult category as obtained from http://cri.univ-tlse1.fr/blacklists/index_en.php . Any idea as to why this is happening?
Thanks for the great package!
-
a very small bug i noticed when on the dnsblacklist.php it has no title and when clicking on the pfsense logo it redirects to a 404.
it redirects to https://domain/packages/dnsblacklist/index.php
instead of https://domain/index.php
works great though, thanks
-
So for instance, if you have facebook.com added to the category of denied hosts, then if anyone tried to resolve the forementioned host name then it would resolve to the IP I currently have set in the config, which is a Google IP.
Hi xa0z. Is there any way to simply return nothing instead of resolving to Google's IP?
-
A very good start, userfriendly. Here are some comments.
- agree with Rezin, or redirect to a configurable error page.
- So is there any LOG showing which URL match which RULES ?
- Once I checked the "Adult", then I cannot visit hk.yahoo.com. I have digged into /usr/local/www/packages/dnsblacklist/blacklists/adult and there are quite a lot of stuffs related to yahoo.
-
Hi,
i've installed pfsense yesterday and try DNS Blacklist, but it seems it doesn't block any site.
i've tried from lan and opt1 interface
each time, the only dns for the client is pfsense
dnsblacklist is activated, and i've checked many categories as adult, games, gamble, etc…
but no success
any idea ?
thanks in advance for your help -
Omichaux,
- Did you have all the LAN client's DNS server changed to the pfSense LAN's IP (the one you used to manage pfSense)
- Did you enable the DNS Forwarder in pfSense which forward all the DNS request to your original DNS server ?
- Did you enable Squid, if so did you changed the DNS server to the pfSense LAN's IP ? Also, it seem every changes made in DNS Blacklist require restart of Squid to made it take effect.
Those are my experience and not sure it fit you case.
-
Thanks for your answer…
but i've already done all of your suggests.
my DNS clients are IP LAN of pfSense
i've reinstall pfsense in version 1.2.3
and reinstall package dns blakclist
squid is not install, but i'm not sure i need it.but no success
-
when is the new updated DNS Blacklist going to be available thanks.
-
Hey guys…
I've not been working on this project as much lately as some other things have come up. I plan to get the next release done before November 8th. Hopefully...
As for people wanting to use a CUSTOM ERROR PAGE, Using dnsmasq, you can only make the hostname they try to resolve into an IP, and then the browser tries to load that IP. For example if you block something like yahoo.com, that means it will make yahoo.com's dns lookup resolve to 74.125.45.100 for example… And then the browser will try to load http://74.125.45.100/ and if that IP doesn't have anything to show the page is blacklisted, then it will only show an error that the request wasn't found. We don't use proxies like Squid. Using this method is faster, but it is kind of limited in that aspect.
All of your comments, and opinions are taken seriously and any requests for fixes, and add-ons are welcome.
-
First off thank you for this excellent package submission.
As for people wanting to use a CUSTOM ERROR PAGE, Using dnsmasq, you can only make the hostname they try to resolve into an IP, and then the browser tries to load that IP. For example if you block something like yahoo.com, that means it will make yahoo.com's dns lookup resolve to 74.125.45.100 for example… And then the browser will try to load http://74.125.45.100/ and if that IP doesn't have anything to show the page is blacklisted, then it will only show an error that the request wasn't found. We don't use proxies like Squid. Using this method is faster, but it is kind of limited in that aspect.
However the device could be forced to redirect to another destination. Could even be locally as pfSense's WebGUI is running on a local webserver.
I believe it is Lighttpd.fwrite($fh2, "address=/" .$line. "/74.125.45.100". "\n");That block of code tells the system as you said that has been blocked where to resolve to. This can be seen in dnsmasq.blacklist.conf file. Each blacklist domain is subsequently followed by the /74.125.45.100 url.
Next I have noticed an issue with dnsmasq.
Not sure if I am doing this wrong either so correct me if I am wrong. I followed this forum thread to fix DNSMasq not restarting without a reboot.
(http://forum.pfsense.org/index.php/topic,11159.0.html)If I have a custom config at /usr/local/etc/dnsmasq.conf it gets overridden by dnsblacklist. The actual config that is written itself is broken:
conf-file=/usr/local/etc/dnsmasq.blacklist.confetc/resolv.confis the result.
Anyways look forward to the update keep up the good work.
With Regards,
Preston -
Hi - firstly thanks for adding this.
Secondly. In case it helps anyone else and saves them the puzzlement it did me, some feedback. I know this kinda repeats some of the above wrt google and facebook, but posting for googlers as the cert thing is new afaik.
Added fine through gui, selected a bunch of likely looking rules and left it running.
User reported "strange messages when trying to login to facebook". Checked.
facebook.com - login screen displayed normally. User enters email address and password and clicks submit;
Firefox displays the wrong cert error;
Secure Connection Failed
login.facebook.com uses an invalid security certificate.
The certificate is only valid for the following names:
google.com , *.google.com(Error code: ssl_error_bad_cert_domain)
(Client running Vista, Error repeats on IE8. Error also repeated on Firefox 3.5 on my Ubuntu machine)
Note google's domain, not facebook. If I forced it to accept, on submitting correct login details to facebook, user was redirected to google.com instead of facebook.
After some fiddling around, I established the problem went away if Dns Blacklist was disabled through the webgui (just the tickbox at the top of it's own settings page).
After some further fiddling, I established that the problem stayed away if I turned on Dns Blacklist, BUT DID NOT SELECT the topmost "Adult (X)" ruleset.
So I can only conclude that something in that particular ruleset is causing this somewhat bizarre certification issue to surface during https or ssl on at least facebook.com (Might happen on other sites, just this was the first)
I hope that's enough to help point towards the problem, and help anyone else encountering this.
-
Fist off I want to say this is a great package! Thanks for all of your work! Sorry if this has already been mentioned, but I would like to see GEO location block options. So for example, if I wanted to block all traffic from URL's ending with *.RU or *.CN, etc.
TNR
-
I would like very much to see this project continue on. Is it in the maybe stage still or will this project be further developed upon? All in all I want to say thank you for the work you have put into this. I've found it useful and would like to see it advanced further to become even better.
-
Hey guys… I'm really glad to hear all the good comments about this package. As almost everyone knows, the issue with this package continuing is the Block List. I would LOVE to make a new release, but until I can compile my OWN list, it just won't happen. I have started on a list, but it's not very big and all of the categories are so large.
As soon as I can get my OWN list compiled and separated then we will be back in business. mcrane has been majorly swamped with his FusionPBX project so I've not even bothered him with this one.
Just everyone who uses this Add-on, hold tight and don't give up on us.
Next release features will include
+Ability to add custom entries
+Ability to bypass individual entries in a blocked category.
+Ability to load local error page (on pfSense)
+Ability to view/edit/modify categories within the GUI (memory intensive) -
Look forward to seeing that :)
Remember to put an country IP blacklist as well….Many an admin would like to see China, Russia and Korea go away...:D