Does the router GL GUI access ok?
How many filtering rules of ADG have enabled?
Please upgrade to the latest firmware v4.7.4 beta to try one more.
Refer to the reply of @buntspext to configure your router.
MT3000's v4.7.4 beta and op24-4.7.0 beta, both have supported to use the MSC Portal.
It does not require to clone MAC, IP, etc. Disable the random MAC on the repeater and DHCP obtain the IP.
Forgot to mention that in my post. Disable adguard, VPN and everything that has to do with DNS resolution.
AdGuard is not working after a few days. When booting the router, and opening AdGuard page it is saying “starting” on the :3000 page. After 5 minutes page :3000 wil not load again.
What can i do?
Try to read the logs and upgrade AdGuard Home using [Script] Update AdGuard Home
Hello,
about my setup: I have some clients that use VPN. These should use the DNS of the VPN provider. This also works without any problems. BUT as soon as I activate Adguard ALL DNS requests are processed by Adguard.
I would like the clients that use VPN to also use the VPN DNS and the other clients without VPN to use Adguard.
Does anyone have any ideas?
i just checked and in any case i get always the IP of my cascading vpn/wg-connection on a Flint 2 with 4.7.4 Beta
I will try thisnout tomorrow. Wil keep you posted.
The VPN IP is correct but the VPN Clients use Adguard and not the VPN DNS.
Is there any plan for a new op24 beta and the bugs above reported, @bruce?
Waiting too 
Come on guys, 4.6.6 it's getting old on me 
1 Like
They have a 4.7.0-op24 too (2 months old).
But the current Beta (closed source wifi driver, based on op21) is already 4.7.4
1 Like
I know, but 4.7.0 never was "trustworthy" for me 
1 Like
I'm the only one with these errors reported on the comment above (and quoted below)? 
Sat Dec 21 14:50:43 2024 user.notice AdGuardHome[29130]: 2024/12/21 14:50:43.146136 [error] dnsproxy: tls://123abc.d.adguard-dns.com:853: response received over tcp: "reading response from tls://123abc.d.adguard-dns.com:853: read tcp 10.14.0.2:57494->94.140.14.49:853: i/o timeout"
Sat Dec 21 14:51:31 2024 user.notice AdGuardHome[29130]: 2024/12/21 14:51:31.728228 [error] dnsproxy: tls://security.cloudflare-dns.com:853: response received over tcp: "reading response from tls://security.cloudflare-dns.com:853: read tcp 10.14.0.2:36284->1.0.0.2:853: i/o timeout"
Sat Dec 21 14:52:02 2024 user.notice AdGuardHome[29130]: 2024/12/21 14:52:02.767526 [error] dnsproxy: tls://security.cloudflare-dns.com:853: response received over tcp: "reading response from tls://security.cloudflare-dns.com:853: read tcp 10.14.0.2:36270->1.0.0.2:853: i/o timeout"
Sat Dec 21 14:53:47 2024 user.notice AdGuardHome[29130]: 2024/12/21 14:53:47.037026 [error] dnsproxy: quic://123abc.d.adguard-dns.com:853: response received over udp: "opening stream: failed to open a QUIC stream: timeout: no recent network activity"
What Bootstrap DNS servers are you using to resolve DoH/DoT?
123abc on the log & servers below is my account on ADGuard/NextDNS
Upstream DNS servers:
[/pool.ntp.org/]9.9.9.10
[/0.openwrt.pool.ntp.org/]1.1.1.2
[/1.uk.pool.ntp.org/]149.112.112.10
h3://dns.google/dns-query
h3://security.cloudflare-dns.com/dns-query
h3://doh3.dns.nextdns.io/123abc/Flint2
https://dns.quad9.net/dns-query
https://d.adguard-dns.com/dns-query/123abc
https://doh.opendns.com/dns-query
https://security.cloudflare-dns.com/dns-query
tls://security.cloudflare-dns.com
tls://123abc.d.adguard-dns.com
quic://123abc.d.adguard-dns.com
8.8.8.8
9.9.9.9
1.1.1.2
Bootstrap DNS servers:
45.90.28.128
1.1.1.2
9.9.9.10
149.112.112.10
2620:fe::10
2620:fe::fe:10
212.159.13.49
@Alisa, as the RC 4.7.4 (OP21) is out now, will the RC for OP24 also be released soon? Thanks.
2 Likes
I see someone already @Alisa, let's wait for her reply.
1 Like
Yes, 4.7.4-op24 will be released soon after 4.7.4 testing is satisfactory.
3 Likes
Does not worth to release 4.7.4 and 4.7.4-op24 on the same time so you will have more users testing it?
For example, I have 4.7.0-op24 installed and I'll not install 4.7.4... I'm waiting for 4.7.4-op24
3 Likes