The adblock-fast which is already in OpenWrt repo and has a WebUI can do everything adblock-lean does and much more with a similar footprint.
You can also use the https-dns-proxy with a customizable adblocking DoH server, that would allow you to use much larger blocklists (as they are hosted off-router), but without customization that adblock-fast allows.
Can you share screenshots? I need to use https://dns.adguard-dns.com/dns-query as DOH resolver. As initial resolver 1.1.1.1 (no google DNS!)
Unfortunately, this is no go for me. I ran into limits and prompted to pay. But I don’t want to pay for DNS…
Can I see its screenshots too? Also can I have detailed guide?
I need to use this https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt and my custom filter to block Google and Facebook crap
Rather than counter this by pointing out flaws in adblock-fast, I will instead write that I think this statement is rather misleading and not entirely in keeping with the friendly spirit of mutual respect that we’ve enjoyed hitherto and I’d like to see remain!
adblock-lean and adblock-fast have different pros and cons and can happily co-exist together without us needing to trade criticisms, right?
I think we should state positively the features that our respective projects have, avoid negative comparisons, and let the users decide for themselves based on their individual use cases.
I would actually just try adblock itself to start with and then see what problems you run into, once it loads into dnsmasq the block lists themselves don't take that much memory - and I've run mid-sized lists on similarly constrained devices (homehub5).
Flash already extended by usb stick. I am talking about RAM and CPU limitations…
As am, I. hence the use of 'memory' rather than 'flash'.
What will you advise? Adblock? Or Adblock fast?
Whatever you can get working - if at that point you run into low memory/cpu issues you can revisit the decision - unless you can quantify the problem though this is just premature optimization. Once they are up and running the adblock* packages work in more or less the same way (a blocklist loaded into a caching DNS server).
Please do, I won't take it personally, if anything it would help make it better.
I'm sorry I haven't kept up to date with adblock-lean development, so I'm probably missing out on some information, but my understanding is that adblock-lean:
is not in OpenWrt repo
implements subset of adblock-fast functionality, ie: can download the dnsmasq conf file, just like adblock-fast can