[Dnsmasq-discuss] About resolution performance and adblock

Ercolino de Spiacico bellocarico at hotmail.com
Mon Nov 25 21:34:47 UTC 2024


The amount of resources we have on a router are very limited. That is 
mainly the reason why we used dnsmasq initially.

Wireless drivers keep us jailed to Kernel 2.6 for the time being, and 
this is also another limitation that could prevent a Pi-hole to be even 
be considered, as backporting is usually a fair bit of work.

Our devices have 32-256MB or RAM with a majority sitting at 128MB

Making adblock working, and not crashing anything else, was not a simple 
task. So we have now something fully operational, but we are now 
pondering the actual performance gone past a certain limit.

If there was a simpler internal dnsmasq modification possible, like the 
one suggested in the other post of this thread, with direct file 
mapping, we would definitely support this instead.

Looking at the bright side, there is a relatively new version of Tomato 
firmware called Tomato64 and this runs on x86 hardware. I'll make sure 
to bring up the pi-hole topic with the relevant people for this version 
at least.

Thanks again for all the info you brought up!



More information about the Dnsmasq-discuss mailing list