I am using uBlock origin on my computer browser, so my main testing devices are two Android phones (Samsung and Mototorla) with Google Chrome and DuckDuckGo respectively, both of which used to work.
I have also tried banip, but the status out of the gate after a fresh installation is error and I can't seem to change that. At this point i think my installation of openwrt hates me or something, LOL.
So, I've reinstalled everything again and it seems to work. The only difference I know of is that I didn't try to set up DoT with Unbound, which is probably what was causing both the problem with banIP staying in an error state and the AdBlock problem.
For now the new setup is: AdBlock with Unbound as a backend (using parallel Dnsmasq) and banIP with the doh blocklist feed.
@dibdot Could you please consider restoring the option to bypass backups? This feature is essential for routers with limited resources, such as low RAM and CPU, as its absence can lead to performance issues. Your attention to this matter would be greatly appreciated
The DNS blocking method is functioning correctly, but it returns the message "Error 9003: DNS name does not exist." In contrast, when I block a domain using the hosts file in the operating system, it returns "Succeeded" and resolves to 0.0.0.0, which is preferable as it prevents repeated attempts to access the blocked domain in some cases.
Is there a way to change the return message to "Succeeded," similar to the behavior of the hosts file? I have attempted to change the "DNS Backend," but only smartdns and dnsmasq are operational, and both still return "Error 9003."
Any guidance or suggestions on how to achieve this would be greatly appreciated!
adblock always returns NXDomain (see readme). Itâs not configurable as itâs the fastest blocking mechanism (in my experience) and the reporting is based on that.
Nope, backups are mandatory in adblock ⌠to ensure fast startups after reboot or interface restarts and to support the etag function (download only lists that that actually changed).
I donât care any crappy routers with less than 128 MB RAM.
Thank you for your insights regarding the adblock functionality. I wanted to share my thoughts on a couple of points.
Currently, using local=/ redirects blocked domains to local DNS, resulting in an Error 9003 or NXDomain response. I believe that using address=/domain/0.0.0.0 is a more effective approach, as it redirects blocked domains to 0.0.0.0. This method can help prevent repeated attempts to access blocked domains in certain scenarios.
Regarding your comment about routers with less than 128 MB RAM, I have a router with 256 MB RAM, but I think it's important to recognize that not everyone can afford high-end routers. Labeling those with less RAM as "crappy" may overlook the diverse needs and budgets of users.
As for the backup feature, I find it consumes extra resources and can slow down the overall process. Since backups are stored in RAM, they become unusable after a reboot. If a user does not have internet access, they typically won't need to block servers. Additionally, if a server is down, relying on an outdated hosts file may not be ideal. Therefore, I believe the backup feature, while intended to enhance functionality, may not provide the benefits it aims for.
I appreciate your work on this and hope we can find a solution that accommodates a wider range of user needs.
Thank you for your kind, considerate, and respectful reply. I appreciate your suggestion regarding using a DNS server with adblocking functionality.
I used to rely on my own script to block domains using dnsmasq, and I primarily use it to block my own list rather than for general ad blocking. While I do have 256 MB of RAM, I've experienced crashes with the backup feature due to hitting the RAM limit.
I find this service convenient for adding new domains to the block list, but overall, using my own script tends to be a better option for my needs. I might also consider utilizing a text file with free sites that allow sharing text to manage my list, as this service doesn't fully meet my requirements.
I bet youâve enabled more subscriptions than you need. I have spoken about that already (you can find it up there somewhere) but in short: Never use subscriptions that were not developed for DNS ad blockers.
I understand your point. However, I believe it would be more beneficial to add an option to bypass backup. Not only do it consumes extra resources, but as I mentioned earlier in details, is often unnecessary.
adblock itself adds close to zero overhead/ RAM usage to your router, BUT the blocklists youâre going to load tend to be huge - and you have to cope with dnsmasq forking for DNS requests over tcp. So if you handcraft your blocklists (a few dozens), thatâs not going to be an issue. However thatâs not what ânormally usedâ (default-) blocklists are (tens- to hundreds or thousands blocked entries), for those 64 MB are insufficient<fullstop>, 128 MB ridiculously small and even 256 MB very tight (and for ipq50xx/ ipq60xx/ ipq807x even 512 MB RAM is very, very tight, as those reserve a lot of RAM for the hardware). If you want effective DNS-based adblocking on your router, you need to throw âsufficientâ RAM at it - or severely adjust your expectations (very few, very small blocklists); this applies to all adblocking implementations for OpenWrt alike, with only marginal differences (the real weight is in the blocklists and dnsmasq deals with them, not the adblock implementation, those just download huge blocklists, do some sanitizing and feed them to dnsmasq).
With not too much own work (good excercise it should be possible to eliminate the backup function from Adblocks code. OR, in case the router in question has a USB connection, to store the backup on a tiny USB stick. For more elaborate users, also having a server on the web, like me, just prepare and store the blocklists over there, to be downloaded after every boot of the router. A minimal VPS for 5E/month is good enough, also allowing setup of my very own VPN or socks5 proxy.
As a contributor to a âcompetingâ adblocking solution, I feel uncomfortable writing this here, however I feel that I need to correct this last part of your post. There is, in fact, a significant difference between adblocking solutions in regards to transient memory use while processing the blocklist and loading it into memory. That transient memory use in some existing solutions is much higher than in others, and this dictates how many domains one can actually load without running into OOM on memory-starved devices. We (myself, @Lynx, @Wizballs and users of adblock-lean) spent a bunch of time and effort to minimize that memory use (in addition to optimizing the backup file size which is admittedly less significant). If differences were marginal as you wrote then all that time and effort was for nothing. As it stands right now (I just made a quick test), I can not load the oisd nsfw list (424,641 domains) with adblock because of OOM, while I can load that list with adblock-lean on my testing x86 VM with 256MiB of memory. Moreover, I can load Hagezi Pro and Hagezi TIF lists (total 672,120 domains) on that same VM with adblock-lean. So I wouldnât say that the difference is marginal. Then if you add Adguard Home to this comparison, likely you could load even smaller number of domains with it.
I have great respect to the work done by @dibdot and developers of other adblocking solutions. Each one has its benefits.
Iâm currently using my own script, which is quite straightforward. It downloads lists, removes comments and duplicate lines, and formats them as address=/domain/0.0.0.0. Right now, Iâm blocking over 900,000 domains, and at no point does the RAM usage exceed 200 MB; it typically runs around 160-170 MB.
Using address=/domain/0.0.0.0 has made my internet experience much faster, and my logs are empty of those 9003 errors. In contrast, when I used the plugin, it was significantly slower in preparing the list and would crash even with a much smaller list.
Here is my hosts file if you'd like to test it; my own domains are excluded. If anyone is interested in seeing my script, I can start a new thread so we can discuss it in detail.
Hi. I think AdBlock is also filtering some github repositories, which is stopping me from getting updates to OpenMediaVault. Is it possible? My blocklists are as follows:
I had attempted whitelisting the domain without success, though I guess that was because I didnât restart the network. After a power cycle it worked. Iâm also running banIP though and disabled that, so doing it might also have been the reason. I really shouldâve isolated those two modifications and I might, during some downtime.