I think I’ve now got it all running okay, I’ll see how it goes from here.
Two questions I would like to verify however.
1 - Am I correct in thinking all filtering is done at device level with no traffic, IPs or URLs being sent to any third party?
2 - Could this in any way cause issues with using Tor Browser? Such as real IP/DNS leak or Tor traffic trying to be filtered despite being encrypted thus not filterable?
Filtering is done on device level, but the DNS resolving needs 3rd party of course. At least if you don’t run your own root DNS server. And I am sure, that you don’t.
No, because the TOR browser does not use any DNS server from your network - TOR bring it own name resolving system.
Is that just the index of blocked content? I assume it just scans through the list each time rather than through connecting through third party resolver?
Good, I am glad for this.
I have just noticed that system memory use is at 93%, isn’t that dangerously high? This was the reason behind my concern relating to accidentally bricking the device and having no means of recovery.
User wants to visit example.org → DNS-Request to DNS-Server (Tell me IP!) → AdGuard Home (Takes domain, checks against the internal lists and forward it to upstream DNS if it’s not inside the lists) → Upstream DNS (f.e. 9.9.9.9) tells “It’s 93.184.216.34”
So you are right if you talk about blocked domain only - these are not forwarded to the upstream DNS. All other domains will be forwarded, ofc.
–
If you enable malware blah, they will send some hashes.
did you upgrade latest version of Adguard Home? if yes then you have high risk because no more space for RAM or storage… GL-inet staff said that.
Flint 2 should be enough RAM and storage, so no problem with Adguard Home
The whole device will explode and burn down your house. Trust me!
Nothing will happen. Normally, the system will try to shovel some data from RAM to cache or will start to kill processes (or they will kill themselves) - so just keep an eye on the functions you need. If they start to have issues, you could check the RAM and the logs.
That sounds a bit spoopy, the VPN could die and it might take me hours to realise. I think I will have to reduce number of lists used or keep it off until I can get a Flint 2.
@slesar do you know if I’m using the right version?
If the VPN on the GL device is WG, it’s highly doubtful that’ll happen. WG is baked into the the mainline Linux kernel tree since 2020-Q1. Just make sure there’s a persistent_keepalive '25' present in the confs.
It’s a different story on the the current (v055a) version of Rethink. That will drop without the addnl setup of Keep it up set to download, delete some web page ever 15 mins or so. That’s my workaround to that known issue. Apparently it’s the same story on the official WG client app for Android.
Yes its WireGuard VPN that I use and the config has a keep alive value of 25 so that all sounds right.
The Rethink option is noted and I’ve bookmarked it but right now I think I want to keep things on the router rather than on devices as it just brings me back to the issue mentioned in my beginning post with netguard.
Hopefully I can get a Flint 2 soonish and won’t have to worry about RAM or CPU since its so beefy.