Openwrt adguard home10/23/2023 What i suggest is to enable NTP logging with the following. 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. Installing AdGuardHome on OpenWrt Community Builds, Projects & Packages Yes, it is possible the opkg version to not start on boot due to race conditions which certain network setups. (edit) My thread and wiki now updated with port 54 instead and updated pictures for rDNS as well as info about reserved ports. I will also make it clearer in my instructions that ports can be changed if required but point out there are assigned ports you should avoid as they are either assigned services or reserved and as a rule you should not use ports that are actively used for other services. If they have, then the nginx reverse proxy method will make the AGH interface available instead. Unless anyone has modified their OpenWrt install, 8080 should be free. Port 8080 for the web interface for AGH is acceptable as Luci runs on port 80 and SSL on 443. MDNS on 5353 is much more likely to be used and thus really should be avoided. While this is an assigned port, its likelihood of being used is low. Despite this port being assigned by IANA, the service is meant to work on SPP (ancestor of IPX/SPX), instead of TCP/IP. Having had a bit to ponder I think I may just redo my instructions and make it so dnsmasq is pushed from 53 to port 54.ĥ4, Assigned, Xerox Network Systems (XNS) Clearinghouse (Name Server). (edit) or would a few extra sections marked optional on the main wiki with the manual thread method be better or more confusing?ĮDIT: In my own AGH edge setup I decided to use port 53000 instead for OpenWrt's builtin dnsmasq port. I need to think about it and maybe ask the admins what their opinion is.Īny opinions from those who have followed my thread/instructions? Feedback is welcome. Yet at the same time I am reluctant to duplicate it as large portions would be the same. You can use my thread with the wiki to do a manual install but you would have to keep checking where the process diverges. Part of me wants to maybe duplicate the wiki and make one that shows the full path for a manual edge install as the thread install is somewhat difficult to read. (Sorry )Īdded in NFT tables replacement for IP Tables rule and link to wiki. Apparently I had fixed the wiki but not my thread. It was causing confusion and I've added a note to that too. I've replaced my PTR picture in my thread to use 192.168.1.1 instead of local lookup. NTP warning enhanced and link to wiki entry. Thus it is HIGHLY preferable your router uses a separate unencrypted upstream DNS to avoid the NTP issue. There is also a race condition with the opkg version due to start up values that is still being resolved. However looping your router DNS through AGH is NOT a recommended configuration for that very reason that NTP lookups WILL fail if the date/time is incorrect. ![]() I've highlighted NTP / SSL warning and made it highly prominent as this has bitten a few people.Moved dnsmasq to port 54 to avoid clashing mDNS 5353 (new) ![]() I've substantially re-edited the wiki to make it flow better.Ī number of sections were moved and also edited so the Table of Contents now properly lists them as subsections.Īdded an updated set of space requirements and example sizes.Īdded in NFT tables replacement for IP Tables rule.Īdded link to AGH page and their logo to the wiki. Install script executes but fails to install as OpenWrt does not have systemds update-rc.d ![]() Using the install script should install AGH and activate the service. Is it possible to either check on if AGH installs correctly as a service and if the systemd method fails then you fall back to init.d method? Or even check the distribution and thus pick either systemd or init.d? 11:43:34 service: executing action "install": Failed to install AdGuard Home service: command "update-rc.d" failed: exec: "update-rc.d": executable file not found in $PATH:Īttempting this manually from the fix thread sudo update-rc.d AdGuardHome defaults Starting AdGuard Home installation scriptĦ 11:43:34 service: control action: install OpenWrt installs fail to install AGH service as OpenWrt do not use systemd's update-rc. However, it appears since was fixed and patched in. I checked to make sure that this issue has not already been filedįYI i'm reporting this on behalf of others as my existing install is fine. I checked th … e documentation and found no answer
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |