#Openwrt adguard home install
#Openwrt adguard home manual
#Openwrt adguard home software
#Openwrt adguard home free

Iptables -t nat -A PREROUTING -i br-lan -p tcp -dport 53 -j DNAT -to 192.168.1.1:5353įeel free to change upstream DNS servers to whatever you like (Adguard Home supports DoH, DoT and DoQ out of the box), add the blacklists of your preference and enjoy ad-free browsing on all of your devices. Iptables -t nat -A PREROUTING -i br-lan -p udp -dport 53 -j DNAT -to 192.168.1.1:5353 Hello everybody, this is a small guide for Adguard Home, an equivalent alternative to Pi-Hole. This step is optional, there are some apps and devices that ship with a harcoded DNS server making AGH useless unless we setup the following iptables rules: Go to Resolv and Hosts Files tab and check the Ignore resolv file option. Login into LuCi and go to DHCP and DNS section, set DNS forwardings to 192.168.1.1#5353. Set DNS server to listen in 192.168.1.1 at port 5353.Ĭreate an user and choose a strong password. Setup the admin web interface to listen in 192.168.1.1 at port 8080. Note that if your router is not at 192.168.1.1 then replace the IP address accordingly.

#Openwrt adguard home install

opt/AdGuardHome/AdGuardHome -s install 2. This router has an arm64 processor but you may need to replace it with the architecture that matches your router (eg armv7, mips, etc), SSH into your router and run: System requirementsĪ router with a recent OpenWrt version installed.įor this tutorial I’m going to use a Belkin RT3200 / Linksys E8450. It operates as a DNS server that re-routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers.Ĭompared to Pi-Hole, Adguard Home doesn’t requires additional dependencies so you can run it on OpenWrt without problems.

#Openwrt adguard home software

After you set it up, it’ll cover ALL your home devices, and you don’t need any client-side software for that. Likewise dnsmasq also defaults to all network addresses by default to bind to.AdGuard Home is a network-wide software for blocking ads & tracking. There is possibly an argument to leave the bind values as default to any available address, because the firewall rules should prevent access outside of the LAN. However one consideration is changing the bind_host/bind_hosts value from 0.0.0.0 could lead to this issue, if you set a specific address that's not available. We could bump the start value a bit, as perhaps 21 is a little too early for all network related areas to be completed, but I wouldn't go as far as increasing to 95.

The edge version installs to /opt/AdGuardHome, the opkg version to /etc jamesmacwhite might be able to help here. OpenWrts opkg version is the stable release.

#Openwrt adguard home manual

The workaround I found is implementing a custom init script that runs before AdGuardHome to make sure other network conditions are available before it tries to start. Introduction: This thread mostly covers the manual installation of AdGuard Homes edge/beta version. I'm not sure the solution is to just increase the START value to 95, as it's way too late in the boot process for something as critical as DNS. I'm wondering if the opkg version should allow you to configure a custom START value in it's config, as currently it will get wiped on any sysupgrade. The issue is these network race conditions aren't always going to happen, it's down to individual setups. The consideration is AdGuardHome devs have made the start value equal to when /etc/rc.local is called, that's right at the end the boot process, which isn't ideal. Short of changing the start value, there isn't an easy fix because it is quite variable. Everything else is replaceable Yes, it is possible the opkg version to not start on boot due to race conditions which certain network setups. Its your config setup that will be personal to you and also any statistics/querylogs you wish to keep. Filters and the program itself can be redownloaded. The yaml file and maybe the stats database are the only really 'key' files in terms of data. (I've been bitten by this with yaml version changes in the past) It is far better to start with a clean install and debug or copy your tweaks to it, than to copy what was working but may be out of date from an old backup. They have stated that config changes will come when they refactor certain modules (eg the DHCP settings etc) My reasoning for this is basically it doesn't take long to re-setup from scratch and AGH is evolving fairly rapidly. Personally i'd just reuse the script to reinstall from clean OpenWrt install and then port any yaml settings from your backup. To use Adguard Home on an OpenWrt router you need at least 20 MB free storage and about 100 MB free RAM (it can be started OpenWrt Forum HowTo Running Adguard Home on OpenWrt. As long as you also re-run the script to move dnsmasq etc. Technically you could just backup the entire /opt/AdGuardHome folder and subfolders and redeploy it back to a new router.