After problems with AdBlock and his reinstalation i see new port forwarding.
Is that right? In older versions of AdBlock were mentioned somewhere only about forward port 53 (I do not know whether it was correct).
AdBlock is not a DNS server, so these rules wonât help you. If you want some to be blocked and some donât, you need to do baypas you donât want to block.
Rule records were created when installing AdBlock - not manually !
When i check or un-check option âRedirect all DNS queries from âlanâ zone to the local resolverâ - setup does not affect firewall redirects setting 53, 853 and 5353.
The conclusion is that the above mentioned redirects are needed for the proper function of AdBlock ?
Typically not AFAIK. So far it seems normal to use local DNS by default, so in those cases it shouldnât make a difference. I personally think this âinterceptionâ isnât worth it, especially for ad-blocking.
BTW, apps can always make it much harder to intercept DNS, especially with the current trends, e.g. Firefox announced (root.cz article) they will âtunnelâ DNS through HTTPS by default (at least in some regions).
Iâve already understood it, youâre right, there is a bug in Adblock - it does not remove the firewall rules - the bug.
No, this option is disabled by default and only useful for rare cases, where connected devices use hardcoded google dns server as resolver (e.g. older android devices).
2 Likes
which adblock version? Not reproducible with current version - please provide the output of /etc/init.d/adblock status
Oh, sorry, I reinstalled AdBlock (luci-app-adblock and adblock) and I canât reproduce the error - I use TOS4. Tested version: 3.5.5-3. Maybe help @JardaB
I am on AdBlock 3.5.1-1 version
While weâre at it - Iâm reporting a bad version identification: package: 3.5.5-3, in /usr/bin/adblock.sh: 3.5.5-2 and LuCI too.
https://repo.turris.cz/hbs/packages/omnia/packages/adblock_3.5.5-3_all.ipk
Same identification in OpenWrt repository.
Thatâs only a cosmetic issue of this release - just ignore it.
I guess I understand how it works. If the status is: âAdblock Status: runningâ, then it must wait until the status is: âAdblock Status: enabledâ, then the option can be pressed again and saved and used. If you do it too quickly and donât wait, the choice will not be made. It would be good if the status is running so that you cannot press âSave and Applyâ.
This is the solution for me.
In the past, if Iâm not mistaken, the adblock installation added port forward rules for ports 53, 853 and 5353. I have now discovered that although I have adblock installed these rules are not there.
I have a my bad memory, is this a bug or is it Ok ?
