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 22.214.171.124
for example... And then the browser will try to load http://126.96.36.199/
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. "/188.8.131.52". "\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 /184.108.40.206 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.
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:
is the result.
Anyways look forward to the update keep up the good work.