What's new

102.7 Alpha Builds available

I also did the update from 102.6 to this alpha build, only on the main AX-11000 pro router.
However with 102.6 the Mesh system behaves like expected, clients get roamed most of the time to the best available Node, with 102.7, only the wired clients are on the nodes, wireless clients seem to be sticking on the main router for some reason, re-connecting the clients has no effect.
Reverting back to 102.6, again wireless clients do roam again to best available node.... mmmm
Some issue with the Mesh system?
Did you try resetting the node(s) (unpair/re-pair). It always seems to be required for my setup on recent versions.
 
Mmm did't do it because it was never an issue before.
Also the wired devices were connected on the nodes, so nodes are recognized and should work.
I'll try again when the beta phase starts.....
 
Mmm did't do it because it was never an issue before.
Also the wired devices were connected on the nodes, so nodes are recognized and should work.
I'll try again when the beta phase starts.....
AiMesh is closed source as far as I know and merlin makes no changes to AiMesh
 
Mmm did't do it because it was never an issue before.
Also the wired devices were connected on the nodes, so nodes are recognized and should work.
I'll try again when the beta phase starts.....
never an issue before doesn't mean it won't happens. if it is the issue with aimesh then i believe it won't just be you alone who encountered it. I myself doesn't have the issue u mentioned. Either u do a reset or there are something wrong with your configurations.
 
Apha 2 builds have been posted earlier this afternoon...
 
Apha 2 builds have been posted earlier this afternoon...
From the change log file in Alpha 2:

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: Merged GPL 102_40399 (GT-BE19000AI only)
- UPDATED: OpenVPN to 2.6.17.
- UPDATED: Dropbear to 2025.89.
- UPDATED: nettle to 3.10.2.
- UPDATED: dnsmasq to 2.93-test2 (includes a couple of DNSSEC
fixes over 2.92)
- UPDATED: openssl-3.0 to 3.0.19 (GT-BE19000AI only)
- UPDATED: Added new 2024 DNSSEC trust anchor, which will
start being used in October 2026.
- FIXED: IPv6 blocking of DoT servers (dave14305)
- FIXED: Multiple minor CVE for OpenSSL 1.1: CVE-2025-68160,
CVE-2025-69418, CVE-2025-69419, CVE-2025-69420,
CVE-2025-69421, CVE-2026-22795 and CVE-2026-22796
(backports by RSDNTWK)
- FIXED: Missing UPnP settings on models with multiservice
WAN support.
- REMOVED: AiCloud support, due to security reasons.

PS: If one want's to compare the change log difference between Alpha 1 and Alpha 2, see the OP post for Alpha 1 change log.
 
Last edited:
Shows empty for me :(
Works fine for me, select the directory of the FW branch you are running .

IMG_6765.png
 
Did today the update to Alpha 2 and AiMesh is now working without any resets of nodes, so was it some glitch or just bad luck with Alpha 1.
 
After updating to Alpha 2, I’m starting to receive this in the logs (RT-BE88U):

“Feb 2 03:03:12 kernel: 192.168.50.217 already exist in UDB, can't add it”
They show up after dnsmasq-dhcp logs, I’m assuming this is normal to show?
 
Dirty upgrade from Alpha 1 to Alpha 2. No issues noted at this time.
 
Did today the update to Alpha 2 and AiMesh is now working without any resets of nodes, so was it some glitch or just bad luck with Alpha 1.
well, nothing was changed with the codes for aimesh i suppose. so most probably the issues was on your side.
 
Alpha 2 just installed. So far, no sweat!!
 

Similar 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!
Back
Top