Closed ntadmin closed 8 years ago
Error in command line options found, now testing
However, although dnsmasq is reading the list, it doesn't seem to be using that; or else dnsmasq isn't actually providing the DNS?
Changed the hosts file entries to 0.0.0.1 (as 0.0.0.0 seems to be some kind of loopback code) but it still seems to go and get the real address.
OK, fake IPs should either be officially listed as never used; OR it should point to the router and the web server on the DGND3700v2 should realise that it is a blocked ad and respond with a simple "add blocked" piece of html.Trying second tack at present.
mini_httpd seems to be controlled rather deeply by the system, so reconfiguring it in some different way is a bit complex ... going back to using an 'known never used' IP (192.51.100.1)
Setting ad servers to a fake, known unused, IP address is now working. (preference 3). This is sufficient for Beta 2, so closing this issue and opening new ones.
Currently, a list of sites to be blocked is downloaded from yoyo, processed and placed in /var/tmp/host.adblock; dnsmasq is configured to read it. However, it doesn't seem to be blocking those domains, as pings to them return valid IPs. ORder of preference for solution:
Once working, we need a control from the web page to turn it on and off. (Not for NEWTB2 though)