102.7 Alpha Builds available

[Setinstone31]

OneDrive

www.asuswrt-merlin.net

Asuswrt-Merlin 3006.xxx Changelog
=================================

3006.102.7 (xx-xxx-2026)
- NOTE: AiCloud has been removed from Asuswrt-Merlin due
to its poor security track record. This also includes
cloud syncing features such as Asuswebstorage or
Dropbox syncing with USB folder. Use a VPN if you
need secure remote access to your data.

- UPDATED: OpenVPN to 2.6.17.
- UPDATED: Dropbear to 2025.89.
- UPDATED: nettle to 3.10.2.
- UPDATED: dnsmasq to 2.92.
- FIXED: IPv6 blocking of DoT servers (dave14305)
- REMOVED: AiCloud support, due to security reasons.

update seemed fine, a little slow at first, but okay. Dirty flash from previous build.

 

[octopus]

OneDrive

www.asuswrt-merlin.net

Asuswrt-Merlin 3006.xxx Changelog
=================================

3006.102.7 (xx-xxx-2026)
- NOTE: AiCloud has been removed from Asuswrt-Merlin due
to its poor security track record. This also includes
cloud syncing features such as Asuswebstorage or
Dropbox syncing with USB folder. Use a VPN if you
need secure remote access to your data.

- UPDATED: OpenVPN to 2.6.17.
- UPDATED: Dropbear to 2025.89.
- UPDATED: nettle to 3.10.2.
- UPDATED: dnsmasq to 2.92.
- FIXED: IPv6 blocking of DoT servers (dave14305)
- REMOVED: AiCloud support, due to security reasons.

update seemed fine, a little slow at first, but okay. Dirty flash from previous build.

Can you remove BETA tag as it is Alpha (3006.102.7 alpha) build. Tks

 

[Blacklistedcard]

Loaded onto BE98Pro. No issue so far.

 

[win465]

BE88U no issues so far.

 

[Treadler]

BE88U no issues so far.

Likewise.

 

[KevinGlynn]

BE86U no issues so far...

 

[octopus]

First try diden't tok, second did. GT-AX6000 all is fine.

 

[Untried3868]

Dirty upgrade (router and node) from 102.6. No issues to speak of.

 

[JakoPako]

BE88U no issues so far.

 

[nzwayne]

GT-BE98Pro & AiMesh units all working after 'dirty' update.

 

[jerry6]

Working well on my 1100 Pro

 

[NiklasO]

I usually don't run alphas but I like the removal of AiCloud. Thanks for that. Working fine on my GT-AX6000.

 

[JJohnson1988]

I'm having an issue with this alpha.

DNS Director set to Router seems to be conflicting with my Android phone that has a private DoT server specified. I can't connect to the Internet while connected to my wireless network whatsoever.

Can I get someone else to replicate this issue? I'm on RT-AX88U Pro, and I have Android 15 with my usual Control D profile specified as Private DNS. The latest stable Merlin for my router does not have this issue.

Edit: The issue goes away when I tell DNS Director "no redirection" for my phone. Alas, I would like the option for my phone to fall back to the router-specified DNS servers in the circumstance where I disable the Private DNS feature on my phone. This is how it has worked for years, until now.

 

[Ripshod]

Can I get someone else to replicate this issue?

Whilst I can't directly replicate your issue I am having a very similar issue. With DNS director set to Router virtually no DNS traffic is going to my pi-hole server. With dns director disabled traffic to the pi-hole is back. This is a complete reverse of what I experienced with the previous releases.
I do note that there is no mention of any changes in the notes.

 

[FLA_NL]

I'm having an issue with this alpha.

DNS Director set to Router seems to be conflicting with my Android phone that has a private DoT server specified. I can't connect to the Internet while connected to my wireless network whatsoever.

Can I get someone else to replicate this issue? I'm on RT-AX88U Pro, and I have Android 15 with my usual Control D profile specified as Private DNS. The latest stable Merlin for my router does not have this issue.

Edit: The issue goes away when I tell DNS Director "no redirection" for my phone. Alas, I would like the option for my phone to fall back to the router-specified DNS servers in the circumstance where I disable the Private DNS feature on my phone. This is how it has worked for years, until now.

I tested this exact case yesterday in 102.6 because I had configured blocking port 853 in the network services but saw somewhere a comment that DNS director already does that and that seem to be the case. I prefer that DNS director blocks this port otherwise devices start to bypass local DNS also if an android phone is configured with automatic private DNS. So this is not new in 102.7. I think making an exception with no redirection for your android is the way to go, the alternative is set your phone to use automatic private DNS.

 

[Tech9]

The issue goes away when I tell DNS Director "no redirection" for my phone.

This is exactly what I would expect to happen on the router side. Your phone's Control D app doesn't allow backup DNS. DNS Director blocks DoT and your phone hangs. This is Control D app issue, if you ask me.

With DNS director set to Router virtually no DNS traffic is going to my pi-hole server.

With your Pi-hole IP address set as usual to "No redirection"?

 

[bennor]

With DNS director set to Router virtually no DNS traffic is going to my pi-hole server. With dns director disabled traffic to the pi-hole is back.

What happens if you set the DNS Director to User Defined #1 and input the Pi-Hole into User Defined #1? This assumes you have properly configured the router to use Pi-Hole. From having the Pi-Hole IP address in the LAN DNS server fields (not the WAN DNS fields) and having the Pi-Hole entered in the DNS Director Client list and configured to No Redirection.

Edit to add: RMerlin made a change a few firmware's back to DNS Director:
3006.102.4 (10-May-2025)
- CHANGED: Setting DNS Director to "Router" will now always
redirect to the router's own IP. Previously it
would redirect to the first DNS server configured
on the DHCP page (which defaults to the router
itself).
If you need DNS Director to redirect to an IP
configured in your DHCP settings, use a Custom DNS
entry in DNS Director. This makes it more consistant
with what the name implies, and was also necessary
for improved Guest Network support.

 

[dave14305]

I'm having an issue with this alpha.

DNS Director set to Router seems to be conflicting with my Android phone that has a private DoT server specified. I can't connect to the Internet while connected to my wireless network whatsoever.

Can I get someone else to replicate this issue? I'm on RT-AX88U Pro, and I have Android 15 with my usual Control D profile specified as Private DNS. The latest stable Merlin for my router does not have this issue.

Edit: The issue goes away when I tell DNS Director "no redirection" for my phone. Alas, I would like the option for my phone to fall back to the router-specified DNS servers in the circumstance where I disable the Private DNS feature on my phone. This is how it has worked for years, until now.

Is IPv6 enabled? A DNS Director bug/loophole was fixed in this alpha. It never used to block IPv6 DoT attempts like it should have. Now it does.

- FIXED: IPv6 blocking of DoT servers (dave14305)

 

[Ripshod]

What happens if you set the DNS Director to User Defined #1 and input the Pi-Hole into User Defined #1? This assumes you have properly configured the router to use Pi-Hole. From having the Pi-Hole IP address in the LAN DNS server fields (not the WAN DNS fields) and having the Pi-Hole entered in the DNS Director Client list and configured to No Redirection.

Previously, with DNS Director set to router the dns settings in the dhcp server (in my case YAZDHCP) were respected. Since installing this alpha that is no longer the case. I have never had to set individual devices up in dns director.

 

[JJohnson1988]

Is IPv6 enabled? A DNS Director bug/loophole was fixed in this alpha. It never used to block IPv6 DoT attempts like it should have. Now it does.

That may have been the reason it was working the way it was, all this time. Took me some time to think about what was going on, but now it makes sense to me.

I have my phone still set to "No Redirection" in the DNS Director as well as Private DNS on my phone set to my Control D profile still, and everything is working like the behavior from before.