What's new

AdGuardHome [RELEASE] Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hi
On my rt-ac86u after a AdGuardHome installation I can connect at internet, but in the gui I see "Stato Internet Disconnesso".
The firmware is 386.4.
It seem not an error but a problem of display. Is it right ?

Thanks for the support.
Stefano
 

Attachments

  • Schermata 2022-01-15 alle 19.58.26.png
    Schermata 2022-01-15 alle 19.58.26.png
    21.8 KB · Views: 67
Hi
On my rt-ac86u after a AdGuardHome installation I can connect at internet, but in the gui I see "Stato Internet Disconnesso".
The firmware is 386.4.
It seem not an error but a problem of display. Is it right ?

Thanks for the support.
Stefano
This was reported in the 386.4 official thread. You may try these commands here to ensure all is looking good:
Also try to restart AdguardHome:
Code:
/opt/etc/init.d/S61AdGuardHome restart
 
Last edited:
This was reported in the 386.4 official thread. You may try these commands here to ensure all is looking goody:

Also try to restart AdguardHome:
Code:
/opt/etc/init.d/S61AdGuardHome restart
Thanks, now It seem ok.
 
Dumb question...I was looking at other forums how some folks setup AdguardHome with Unbound and my question is...when updating the AdguardHome Upstream DNS servers, does it make a difference if the entry is submitted with or without these [//] symbol:

Code:
[//]127.0.0.1:53535
or
127.0.0.1:53535

I tried both and I don't think I've notice any difference, just curious why some have the symbol and others don't. Thanks!
I would stick with the original directions. [//] is used to imply something, which is covered by
[//]192.168.1.1:553

(your routers ip address).
 
Dumb question...I was looking at other forums how some folks setup AdguardHome with Unbound and my question is...when updating the AdguardHome Upstream DNS servers, does it make a difference if the entry is submitted with or without these [//] symbol:

Code:
[//]127.0.0.1:53535
or
127.0.0.1:53535

I tried both and I don't think I've notice any difference, just curious why some have the symbol and others don't. Thanks!
I found that there must be an entry without the leading square bracket before I can click the apply button without getting an error message.

I have unbound and diversion. For the time being, I have comment out the default 9.9.9.9 and 127.0.0.1:553; leaving 192.168.1.1:553. When I click Test Upstreams it gives me an error. But I can click Apply button. With this I can see dns query logged in dnsmasq.log. Diversion will now work along with AGH.
 
Last edited:
I found that there must be an entry without the leading square bracket before I can click the apply button without getting an error message.

I have unbound and diversion. For the time being, I have comment out the default 9.9.9.9 and 127.0.0.1:553; leaving 192.168.1.1:553. When I click Test Upstreams it gives me an error. But I can click Apply button. With this I can see dns query logged in dnsmasq.log. Diversion will now work along with AGH.
yea I have been running mine for several weeks with no errors, complaints, or issues. no "special quirks" either. To be clear, I run mine with whatever the default installer puts, plus I changed my dns servers to run pointed at unbound instead of the 8.8.8.8 and the 9.9.9.9.
 
Noticed something weird with DNS TTL. I have unbound cache-min-ttl: 3600

Within the router, I can see TTL gets refreshed before it times out.
Code:
admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18742
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             263     IN      A       142.251.10.139
google.com.             263     IN      A       142.251.10.138
google.com.             263     IN      A       142.251.10.113
google.com.             263     IN      A       142.251.10.101
google.com.             263     IN      A       142.251.10.100
google.com.             263     IN      A       142.251.10.102

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:43 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37515
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3598    IN      A       142.251.10.139
google.com.             3598    IN      A       142.251.10.100
google.com.             3598    IN      A       142.251.10.102
google.com.             3598    IN      A       142.251.10.113
google.com.             3598    IN      A       142.251.10.138
google.com.             3598    IN      A       142.251.10.101

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:45 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root#

However, in my pc, the TTL does not refresh and keeps going down to 0. Then it resumes the TTL value from router. Before AGH, pc TTL will refresh just like the router.
Code:
C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23977
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             249     IN      A       142.251.10.138

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:09:57 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20118
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             33      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:33 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55

C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18804
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             24      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:42 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3285
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3293    IN      A       142.251.10.138

;; Query time: 271 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:14:50 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55
 
Noticed something weird with DNS TTL. I have unbound cache-min-ttl: 3600

Within the router, I can see TTL gets refreshed before it times out.
Code:
admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18742
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             263     IN      A       142.251.10.139
google.com.             263     IN      A       142.251.10.138
google.com.             263     IN      A       142.251.10.113
google.com.             263     IN      A       142.251.10.101
google.com.             263     IN      A       142.251.10.100
google.com.             263     IN      A       142.251.10.102

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:43 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37515
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3598    IN      A       142.251.10.139
google.com.             3598    IN      A       142.251.10.100
google.com.             3598    IN      A       142.251.10.102
google.com.             3598    IN      A       142.251.10.113
google.com.             3598    IN      A       142.251.10.138
google.com.             3598    IN      A       142.251.10.101

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:45 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root#

However, in my pc, the TTL does not refresh and keeps going down to 0. Then it resumes the TTL value from router. Before AGH, pc TTL will refresh just like the router.
Code:
C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23977
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             249     IN      A       142.251.10.138

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:09:57 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20118
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             33      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:33 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55

C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18804
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             24      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:42 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3285
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3293    IN      A       142.251.10.138

;; Query time: 271 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:14:50 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55
did you disable the cache on AdGuardHome? or are you using it? are you manipulating the TTL with AdGuardHome? I disable the cache on AdGuardHome, and I let it use the one issued by Unbound.
 
Noticed something weird with DNS TTL. I have unbound cache-min-ttl: 3600

Within the router, I can see TTL gets refreshed before it times out.
Code:
admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18742
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             263     IN      A       142.251.10.139
google.com.             263     IN      A       142.251.10.138
google.com.             263     IN      A       142.251.10.113
google.com.             263     IN      A       142.251.10.101
google.com.             263     IN      A       142.251.10.100
google.com.             263     IN      A       142.251.10.102

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:43 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root# dig @127.0.0.1 -p 53535  google.com

; <<>> DiG 9.17.20 <<>> @127.0.0.1 -p 53535 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37515
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3598    IN      A       142.251.10.139
google.com.             3598    IN      A       142.251.10.100
google.com.             3598    IN      A       142.251.10.102
google.com.             3598    IN      A       142.251.10.113
google.com.             3598    IN      A       142.251.10.138
google.com.             3598    IN      A       142.251.10.101

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53535(127.0.0.1) (UDP)
;; WHEN: Thu Jan 20 00:09:45 MYT 2022
;; MSG SIZE  rcvd: 135

admin@RT-AC86U-DBA8:/tmp/home/root#

However, in my pc, the TTL does not refresh and keeps going down to 0. Then it resumes the TTL value from router. Before AGH, pc TTL will refresh just like the router.
Code:
C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23977
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             249     IN      A       142.251.10.138

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:09:57 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20118
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             33      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:33 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55

C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18804
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             24      IN      A       142.251.10.138

;; Query time: 2 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:13:42 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55


C:\>dig google.com

; <<>> DiG 9.16.12 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3285
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             3293    IN      A       142.251.10.138

;; Query time: 271 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 20 00:14:50 Malay Peninsula Standard Time 2022
;; MSG SIZE  rcvd: 55
From what it looks like, AdGuardHome is not refreshing entries. (it doesn't have a prefect policy like Unbound). Don't worry your responses between AdGuardHome and Unbound should still be refreshed though. so you should turn off or disable AdGuardHomes Cache.
 
did you disable the cache on AdGuardHome? or are you using it? are you manipulating the TTL with AdGuardHome? I disable the cache on AdGuardHome, and I let it use the one issued by Unbound.

From what it looks like, AdGuardHome is not refreshing entries. (it doesn't have a prefect policy like Unbound). Don't worry your responses between AdGuardHome and Unbound should still be refreshed though. so you should turn off or disable AdGuardHomes Cache.

I have not change the default setting. Will look it up and disable AGH cache.
 
After set cache bytes to 0, client DNS TTL behavior back to normal.
That confirms my thoughts, you were digging off of AdGuardHomes cache, and not Unbounds. Do you see any web page differences? does it impact what ads are blocked now that you disabled the cache, or does it seem to function still the same?
 
That confirms my thoughts, you were digging off of AdGuardHomes cache, and not Unbounds. Do you see any web page differences? does it impact what ads are blocked now that you disabled the cache, or does it seem to function still the same?
Yes, you are right. With AGH cache disabled, client go directly to unbound cache. In terms of adblock I think it works the same after disable the cache. I still run diversion in parallel. So after AGH, the DNS query still have to go through diversion. I am seeing much less hit in diversion now that most are blocked by AGH. I am just using the default list in AGH. Probably over the weekend I will copy my list from diversion into AGH.
 
@SomeWhereOverTheRainBow
Can a feature to use the latest beta and edge versions (of AGH) be included?

Or some direct command to use the beta/ edge variant instead of the stable binary and revert if needed.

Router: AX-88U, running latest 386.4
 
As for the logs you are seeing with AdGuardHome, that looks like something you may want to query AdGuardHome about. it could just be handshakes. From My understanding, AdGuardHome fakes those IP's in the syslog so it doesn't actually show the real IP, but I would query over to AdGuardHomes github and ask someone a little bit more knowledgeable on their applets practices. Not sure about the timeouts though. It probably has to do with the device or adguardhome failing to close the connection.

If you are able to load pages I wouldn't worry to much about it.

Hi, as you suggested I headed over to the adguard-github with the issue (see the thread here ) - now they fixed it in the edge version (by hiding it behind debug-level) and asked me to test if its working this way ...

so - now my question - how do I get the latest edge-version here on my asuswrt-merlin with your script and/or without breaking something else?

Thanks again
best regards

PS - I just saw a similar question over my reply - sorry for that
 
Hi, as you suggested I headed over to the adguard-github with the issue (see the thread here ) - now they fixed it in the edge version (by hiding it behind debug-level) and asked me to test if its working this way ...

so - now my question - how do I get the latest edge-version here on my asuswrt-merlin with your script and/or without breaking something else?

Thanks again
best regards

PS - I just saw a similar question over my reply - sorry for that
I guess the easiest way is to
- download the appropriate edge/ beta version directly from github
- stop AdGuardHome
- Overwrite the AdGuard Home directory
- Restart AdGuard Home

Edge version for RT-AX88U should be... Linux arm 64-bit - Edge

So commands something like....
Code:
wget https://static.adguard.com/adguardhome/edge/AdGuardHome_linux_arm64.tar.gz
/opt/etc/init.d/S61AdGuardHome stop
tar xzv -C "/opt/etc" -f "AdGuardHome_linux_arm64.tar.gz"
rm AdGuardHome_linux_arm64.tar.gz
/opt/etc/init.d/S61AdGuardHome start

... and this should get you the edge version of AdGuard Home.
 
[
I guess the easiest way is to
- download the appropriate edge/ beta version directly from github
- stop AdGuardHome
- Overwrite the AdGuard Home directory
- Restart AdGuard Home

Edge version for RT-AX88U should be... Linux arm 64-bit - Edge

So commands something like....
Code:
wget https://static.adguard.com/adguardhome/edge/AdGuardHome_linux_arm64.tar.gz
/opt/etc/init.d/S61AdGuardHome stop
tar xzv -C "/opt/etc" -f "AdGuardHome_linux_arm64.tar.gz"
rm AdGuardHome_linux_arm64.tar.gz
/opt/etc/init.d/S61AdGuardHome start

... and this should get you the edge version of AdGuard Home.
Or just wait until later today when I get time to patch the installer.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top