You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AdAway is a FOSS DNS manager on Android used primarily for ad-blocking, it can also be used to block any other websites.
While the script has no issues just by reading & running it, AdAway can't pick up on these Tor nodes and thus can't be blocked by the app. I'd like to know if this is something to do with the IP addresses on this repo, my script, or the Android app itself.
It should display "X Hosts", where X is the sum of all IP addresses blocked using the host source. However, that doesn't get displayed and thus none of the Tor nodes get blocked on my Android phone. And I'd like to know what could be causing it.
FYI I've already filed an issue on the AdAway GitHub repo to also find help from the app developers, too. Looking to find solutions from all sides.
Thanks in advance.
Screenshots of this unusual behavior:
The text was updated successfully, but these errors were encountered:
Hi. I tried converting the .lst file into a .txt file using a Python script I made a few hours ago with all the necessary redirects for use on AdAway.
AdAway is a FOSS DNS manager on Android used primarily for ad-blocking, it can also be used to block any other websites.
While the script has no issues just by reading & running it, AdAway can't pick up on these Tor nodes and thus can't be blocked by the app. I'd like to know if this is something to do with the IP addresses on this repo, my script, or the Android app itself.
You may reproduce the results with the following:
It should display "X Hosts", where X is the sum of all IP addresses blocked using the host source. However, that doesn't get displayed and thus none of the Tor nodes get blocked on my Android phone. And I'd like to know what could be causing it.
FYI I've already filed an issue on the AdAway GitHub repo to also find help from the app developers, too. Looking to find solutions from all sides.
Thanks in advance.
Screenshots of this unusual behavior:
The text was updated successfully, but these errors were encountered: