[ 3006.102.6 alpha Build(s) ] available build(s)

[jksmurf]

Maybe similar issues with Client Device presentation.

RT-AX88U Pro, alpha1 (alpha2 not available yet for that model), RT-AX3000 Node with 388.10_2.

Main 3006.102.6_alpha1-gc3ecf6dda6 (16Oct25)
Node 3004.388.10_2

I am also seeing disparities in network map vs previous FW (only 17 vs about 24 devices) AiMesh showing 17 too, Wireless log is however showing some of my ESP32 devices which I know are connected but are not showing up in the Network Map or AiMesh, and at least one of my Wired Device is not showing at all (on Primary network), whereas wired devices on Guest networks are showing up OK. Just odd.

Can supply logs if needed.

[EDIT 1] Reverting to 3006.102.5 brought back the client numbers I expected and also the wired device on Primary and then updating to the older alpha1 3006.102.6_alpha1-g2480b89a4a (10Oct25) stayed the same.

[EDIT 2] Seems to have been an IPv6 Issue. Still investigating but if I disable this on IoT_Guest it seems to work.

 

[X3wKNkGk]

I tried to upgrade to alpha 2 for be86 (RT-BE86U_3006_102.6_alpha2-g683db26d11) but it wasn't done with the upgrade after it rebooted itself.
But it successfully upgraded to alpha 1 (RT-BE86U_3006_102.6_alpha1-g5507234591)
Not sure if there's something wrong here, I was trying to upgrading it from 3006.102.5 btw

I attempted to flash it via hnd-write command via ssh and it seems like it was just soft-bricked. I ended up using restoration utility to flash it back to 3006.102.5

 

[Katana1074]

I tried to upgrade to alpha 2 for be86 (RT-BE86U_3006_102.6_alpha2-g683db26d11) but it wasn't done with the upgrade after it rebooted itself.
But it successfully upgraded to alpha 1 (RT-BE86U_3006_102.6_alpha1-g5507234591)
Not sure if there's something wrong here, I was trying to upgrading it from 3006.102.5 btw

Confirmed, same happened to me....

 

[KevinGlynn]

Confirmed, same happened to me....

... and me

 

[visortgw]

RT-BE88U with alpha2.
Network Map AND GNP showing no wireless devices connected. Specific to network map wireless devices are showing as "wired". Devices are connected in Wireless Log and I'm posting this from my connected phone.
View attachment 68733View attachment 68734

FYI, no such issue with GT-BE98 Pro.

 

[Wisiwyg]

No issue with BE96U

 

[JakoPako]

RT-BE88U with alpha2.
Network Map AND GNP showing no wireless devices connected. Specific to network map wireless devices are showing as "wired". Devices are connected in Wireless Log and I'm posting this from my connected phone.

Same problem. I don't have any WiFi devices shown. For me, everything is also like cable. RT-BE88U - alpha2.
Edit: Back to alpha1 - OK

 

[cc666]

Installed the latest Beta 2 on GT-BE 98PRO. Full reset, manualy inputted all settings.
Log loaded with this:

kernel: External auth failed with status = (15)

Any ideas?

CC

 

[MDM]

Installed the latest Beta 2 on GT-BE 98PRO. Full reset, manualy inputted all settings.
Log loaded with this:

kernel: External auth failed with status = (15)

Any ideas?

CC

Google - 2 sec =
Wi-Fi authentication reject on Linux status_code=15 and Reason 15 is “4-Way Handshake timeout”.

Basically some device cannot connect...

 

[cc666]

Google - 2 sec =
Wi-Fi authentication reject on Linux status_code=15 and Reason 15 is “4-Way Handshake timeout”.

Basically some device cannot connect...

Fixed the problem. Now it running perfectly. The log (with notice) is clean. Everything is quick and stable. Great release.

CC

 

[jksmurf]

Fixed the problem.

How, please? Not for me but for others.

 

[Blacklistedcard]

Same problem. I don't have any WiFi devices shown. For me, everything is also like cable. RT-BE88U - alpha2.
Edit: Back to alpha1 - OK

BE98Pro with the latest firmware. Confirming I don't have this problem.

 

[win465]

So it seems like the BE88U latest alpha is the ones experiencing Aimesh not working properly and wifi devices not showing properly.

 

[cc666]

How, please? Not for me but for others.

I had made a mistake on one of the wifi channels by inverting 2 digits in the pw. Therefore wireless devices were constantly trying to connect and getting rejected. Once I fixed the pw all is perfect

cc

 

[Milan]

So it seems like the BE88U latest alpha is the ones experiencing Aimesh not working properly and wifi devices not showing properly.

Same here - seems some issue with AIMesh:

Other stuff working fine.

 

[S.claus]

BE88u Alpha 2

VLAN page under LAN is broken. I can set a profile but the VLAN page itself doesn't load

Getting log spam 3627 : notify_rc start_amas_lanctrl & 3627 : notify_rc start_cfgsync

 

[RMerlin]

Asus included the wrong wireless dongle firmware in the RT-BE88U GPL. This causes hardware authentication to fail (RT-BE86U != RT-BE88U), so any feature that valides that you are running on genuine hardware (like AiMesh) will refuse to start. You can thank the Netgear and Xiaomi illegal firmware ports for these hardware validation measures.

I will need to retrieve the correct dongle firmware from their recent firmware releases, which should be close enough - will be faster than asking them for fixed versions if they do work.

In the meantime I removed both test builds (the dongle firmware included in the RT-BE86U also looked suspicious to me).

 

[penguin22]

Asus included the wrong wireless dongle firmware in the RT-BE88U GPL. This causes hardware authentication to fail (RT-BE86U != RT-BE88U), so any feature that valides that you are running on genuine hardware (like AiMesh) will refuse to start. You can thank the Netgear and Xiaomi illegal firmware ports for these hardware validation measures.

I will need to retrieve the correct dongle firmware from their recent firmware releases, which should be close enough - will be faster than asking them for fixed versions if they do work.

In the meantime I removed both test builds (the dongle firmware included in the RT-BE86U also looked suspicious to me).

Honestly appreciate you finding this so quickly and for those that installed and identified the issue having done so. This is exactly why these Alpha versions exist. I held off on the BE88U (my main router and only one running Merlin) to see the feedback from some other testers, as I have had some stability issues with my BE86U running the official stock firmware just released.

Is it likely that this incorrect wireless dongle firmware is present in the official BE86U release from Asus as well?

 

[RMerlin]

Honestly appreciate you finding this so quickly and for those that installed and identified the issue having done so. This is exactly why these Alpha versions exist. I held off on the BE88U (my main router and only one running Merlin) to see the feedback from some other testers, as I have had some stability issues with my BE86U running the official stock firmware just released.

I rarely reply to test builds posts, but I do keep track of them, bookmarking posts that require closer analysis. They act as a smoke test for me during early development.

Is it likely that this incorrect wireless dongle firmware is present in the official BE86U release from Asus as well?

No, since their firmware compile the dongle firmware during the build process. The error was when they generated the GPL archive they sent me, they included the wrong copy of that precompiled file.

 

[RMerlin]

Updated builds have been uploaded, with the correct dongle firmwares.