![]() ![]() DietPi-Services | dietpi-wifi-monitor inactive (dead) DietPi-Services | dietpi-postboot active (exited) since Thu 21:03:25 BST 1min 59s ago DietPi-Services | dietpi-boot active (exited) since Thu 21:03:25 BST 1min 59s ago DietPi-Services | dietpi-preboot active (exited) since Thu 21:02:22 BST 3min 2s ago DietPi-Services | dietpi-ramlog active (exited) since Thu 21:02:22 BST 3min 3s ago DietPi-Services | dietpi-vpn inactive (dead) DietPi-Services | adguardhome active (running) since Thu 21:03:25 BST 1min 59s ago ![]() DietPi-Services | unbound active (running) since Thu 21:03:20 BST 2min 5s ago Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of rvice changed on disk. DietPi-Services | dropbear active (running) since Thu 21:03:25 BST 1min 59s ago DietPi-Services | cron active (running) since Thu 21:03:26 BST 1min 59s ago ![]() DietPi-Services | shairport-sync active (running) since Thu 21:03:26 BST 1min 59s ago DietPi-Services | avahi-daemon active (running) since Thu 21:03:26 BST 1min 59s ago Based upon that fact that I am a user with basic knowledge I would say that both products provide the LAN DNS blocking I wanted but AdGuard Home was slightly easier to setup and the Admin interface is setup more logically for my use.Īgain unless you want to spend the time and learn new things testing over a VM or Docker container then spend the $60 for a RPI 4 or even less for a used older model on ebay.Hi, Joulinar, here’s the output: DietPi-Services I also went thru the same setup last week and put Pihole on the same RPi and ran it for a couple days. The defaults will provide the basic DNS blocking on your LAN and if you want to customize then you can spend more time learning how to modify the defaults. The setup is simple and require little knowledge to get going. I happen to have a old RPi model B laying around so yesterday I made a image of the RPi headless OS and followed the ADGuard install instructions (many around) and I had it up and working in less than 30 minutes. They cost so little that it is not worth your time to fool around trying to learn about VM and Docker containers just to examine AdGuard Home. I would just go out and buy a Raspberry Pi. Give it a try in a virtual machine or Docker before spending out on hardware. I have run my own AdGuard Home (and PiHole before that) for years, and wouldn't go back. It's more work, but for the technically inclined it's much more acceptable to run it on-prem rather than rely on someone else's implementation, especially where latency and speed are priorities. You can choose which clients on your network (or the Internet) can connect, what services they can access, and which lists apply to them. If something doesn't work, you get to fix it exactly how you like (eg whitelisting). With running AdGuard Home, you control what block lists are installed, who can connect and how, what upstreams are used, and how it all fits together. They control it, they choose the block and allow lists, and you just get to connect and use it how they intended.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |