AGH does use SSL for encrypted DNS but that is separate to the web interface. If you wish to use SSL for AGH you will need to move Luci or run AGH on non standard ports. Luci (OpenWrt's web interface) runs on port 80 and port 443 for SSL. AGH supports encrypted DNS internally and it is just a matter of choice as to which method you use and what servers you put in.
Please ensure you edit any scripts to match your config or this will break things in bad ways. My installation uses 192.168.1.1 as default IP. Raspberry Pi Zero as a router-attached ethernet gadget This gives AGH a separate cpu to run on if your router is older and lacks space and power. He kindly wrote up about using a pi zero off the USB port router piggy backing on OpenWrt. With careful setting of options you can keep the requirements low but having an entire USB drive to use will avoid issues.Īnother interesting option is what uses. Add in filters, DNS queries, Stats, (and a 2nd copy of AGH binary when it updates and backs up) and your space rapidly vanishes. Mounting it as /opt/AdGuardHome will ensure you do not run out space on smaller routers. NextDNS - It is recommended to use AGH as a better client for NextDNS : Installing AdGuardHome on OpenWrt - #6 by mercygroundabyssįor limited space routers you can mount a USB drive and use that to host AGH. You are free to edit the scripts to use your own ports but you should check with for reserved ports. The ports chosen are either well known alternate ports or reasonable compromises. The edge version installs to /opt/AdGuardHome, the opkg version to /etc/adguardhome for the config files and /tmp for filters, logs etc thus you WILL loose them when your router reboots. OpenWrt's opkg version is the stable release.
#Adguard dns for router manual
This thread mostly covers the manual installation of AdGuard Home's edge/beta version.
0 kommentar(er)
