I'm having some trouble controlling adblock (suspending, resuming, enabling, disabling), from both CLI and luci.
I'm using a pretty fresh install of OpenWrt 21.02.3 (I didn't upgrade, I installed clean). Adblock 4.1.3.
I wasn't able to suspend by clicking "suspend" in luci or /etc/init.d/adblock suspend on the CLI. Eventually service adblock suspend seemed to have suspended it.
Now I can't start it again. Whether I use /etc/inti.d/adblock enable, /etc/inti.d/adblock start, /etc/inti.d/adblock restart, service adblock enable, service adblock start, service adblock restart, nothing seems to change the status.
Luci shows the status as disabled, but there's no enable button, just suspend, reload, restart. service shows the line /etc/init.d/adblock *enabled* stopped service adblock status shows + adblock_status : *disabled*
which to me seems conflicting.
I thought it might have been working by rebooting the router, but that doesn't seem to change anything.
I'm probably doing something dumb, but I don't know what it is!
Hi everyone. I'm having some issues with AdBlock while using DNS HTTPS Proxy. I feel like it's not working all that well.
I get the following results on these tests: https://d3ward.github.io/toolz/adblock.html - I get 10% Blocked Hosts https://adblock-tester.com - I get 36 points out of 100
On adblock, I checked Force Local DNS on LAN and Force Port: 5353 which is the DNS HTTPS Proxy port.
What am I missing here? Which results should I normally get on those tests?
Thanks in advance!
Depends solely on your blocklist selection, e.g. on your first link I receive 100% on the second link I receive 83%. The latter one includes page element tests (e.g. gif image tests) which can't be fulfilled by dns based blocking tools.
BUG Report:
After upgrading from Openwrt 21.02.3 to 22.03.0, Adblock 4.1.4 consistently gives an error and stops working after router (re)boot or after an /etc/init.d/adblock restart. The DNS backend is Unbound which is properly working.
logread -e adblock shows: (...) user.info adblock-4.1.4[5690]: adblock instance started ::: action: start, priority: 0, pid: 5690 (...) user.err adblock-4.1.4[5690]: dns backend restart with adblock blocklist failed
Strange, works for me with unbound. Please enable debug logging in adblock, remove your adblock backup files and do a full restart. Send the full adblock- and unbound-related logs - thanks.
I had "example.com" on the local adblock blacklist. Removing it seems to have solved the problem.
I wonder why the "example.com" behavior changed from Adblock v.4.1.3 to v.4.1.4. Is it a bug, or is it "by design" ?
Well, that's expected if you block the standard dns lookup domain (for whatever reason). You could change the lookup domain (adb_lookupdomain) or disable this check at all (set the parameter to false ... also described in the readme (see first post).
Ok. I did set adblock.global.adb_lookupdomain='one.one.one.one' and re-added example.com to my adblock blacklist. All seems to be working well again.
Thank you.
Thanks a lot for this adblock app. I've set my scheduled actions perfectly now. I've moved to this adblock on openwrt from having 2 pi-holes and so far so good!