Quote:
Originally Posted by RogerSC
Seems like it'll be fun to play with, might give it a go and see if can improve things for devices that don't have ad blocking, like my Android phone.
|
As for me, I redirect all http traffic from Android tablet to privoxy transparent proxy on router with original AdBlock rules.
For what? The embedded browser is real fast but can't use plugins, a firefox got AdBlock plugin but it's slow as hell.
If someone interested, I'll write How-to about that. This solution is quite universal: no matter iOS or Android devices will be used.
Quote:
Originally Posted by RogerSC
Curious if it'll slow things down much.
|
Yes, all DNS "improvements" needs to be benchmarked. As for DD-WRT variant above, there is
strings in blacklist. It will not slow down dnsmasq. But if blacklist will be greater, taken from
adsuck for example:
Quote:
$ wc -l /opt/etc/adsuck/Hosts.pub
130063 /opt/etc/adsuck/Hosts.pub
|
then dnsmasq will consume +8MB RAM and will add delays to DNS resolving.
The second disadvantage of dnsmasq + hosts blacklist is following: every time browser "asks" for blacklisted domain, dnsmasq returns "127.0.0.1", which means "this PC" so every time browser will wait for answer from local PC, where no web server is installed.
There is another solution for hosts-based blacklists:
adsuck. Adsuck is a DNS server which immediately returns NXDOMAIN (non existent domain) answer for black listed domains. So browser caches it's answer and not trying to get blocked elements again and again.