Request to create page for AdGuard Home (Under DNS section)

There's a lot of useful information on the forum about running AdGuard Home on OpenWrt, however there is currently no wiki page for it.

Would someone with the relevant access be able to create a stub page? I don't have access to create a page by the looks of it, just edit options on existing.

I think it would be great to preserve and expand on the work of community members and ensure there's a single source of documentation for running AdGuard Home on OpenWrt.

1 Like

Placeholder bolted up. Wikifying of my thread in a bit.

1 Like

Amazing! That should help preserve everything written so far into a single place. Once the wiki is sorted, we can reach out to AGH to see if they want to link to any OpenWrt specific installation instructions on their Wiki. They seem to have a couple of articles for Pi-Hole and Docker

As long as we keep feeding issues with OpenWrt back into AGH via issues then they should be managed and deployed as edge builds. I got a few things sorted by detailing and I saw some other OpenWrt fixes that others requested (Divested builds were improperly id'd for instance)

Now 107 is a stable release and opkg'd properly it should be fairly simple install and go. I'll have to do some testing and see what differences there are between the opkg variant and using the scripted version that I detailed as part of the forum thread.

Absolutely, it should benefit everyone with actively feeding the issues upstream and maintaining the official package. Once the next build of packages happens the 107 release through opkg will make it a lot simpler to install and will ship a working binary. I don't know if the compile options through OpenWrt will help reduce the overall size. The binary taken directly from GitHub (in my case armv7) is now around 32 MB, before is was about 20 MB. That's potentially a consideration to note for routers will less flash space and why the Wiki and guides are good for this potential edge cases.

Configuration recommendations like not chaining AGH as an upstream from dnsmasq is a good thing as well. I was doing this until I saw the comments on your guide and tested the latency and dropped it by over 10ms. Likewise more exotic features like ipset, which is a common setup with dnsmasq these days can also be ported to AGH, so having those on the Wiki will really help users get the best configuration from the beginning. The ipset syntax isn't actually that clear on the official guides, so again helping user transition is where the wiki can come into play.

As you've put in a lot work I won't do anything, but happy to assist with maintaining the wiki is you'd like.

The space issues were one of the things I brought up to the AGH team, also the logging and not checking diskspace before upgrading. To be fair to them however, AGH was aimed at "bigger" computers/routers. More x86 board etc rather than integrating into OpenWrt builds. It is certainly possible but its borderline for some routers. I was using a 128mb bt hub 5 and it more or less managed ok. There is no WAY you would do that with smaller routers (eg single core or low powered dual cores) or routers with tiny flash spaces without doing some sort of usb key install (and thus having do either exroot or a mounted usb key via directory)

(edit - )

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.