Got it working had to remove some domains after that it was processed and merged successfully
1 Like
By the way is there a way to block domains for certain clients and allow domains for certain clients is that a thing or is planned to be there in the future?
The next version which is (still) being worked on will support having any number of independent "blocksets", i.e. final blocklists using the terminology of the current version of adblock-lean. You will be able to assign certain dnsmasq instances individually to each blockset - this way, you could implement different filtering for different network segments. Not exactly per-client config but may work for this case if e.g. you group such clients in vlans or configure a group of clients to use a different port for DNS resolution.
1 Like
Thanks! That sounds really useful. I already have my networks separated, so I think this will make things much easier. Looking forward to the update. 
1 Like
How are clients identified ? I.e. by using different SSIDs, or unique identification by (non-randomized) MAC ?
Non-Randomized MAC's
Yep, can be done. My private (commercial) project for years, but in the context of parental control. Which is practically same as ad blocking. However, using a completely different approach, which is DB-based for full flexibility and implemented with a customized DNS resolver (powerdns). And therefore, needs more resources (RAM, 128MB min., depending upon owrt version).
Ohh! I see the setup I got is like this and I got like 250+ MB RAM free to spare and these services running know OpenWrt 25.12.5
RBR50V1 is my main device
https-dns-proxy - DoH
adblock-lean - Adblocking
pbr - Route Wireguard
Tailscale - Remote Access because CG-NAT
QoSmate - Shaping
banIP
Sorry for if I went off-topic