What's new
  • 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!

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

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.
 
Last edited:
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
 
Last edited:
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....
 
No issue with BE96U
 
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
 

Attachments

  • 01.jpg
    01.jpg
    13.6 KB · Views: 18
  • 02.jpg
    02.jpg
    14.2 KB · Views: 12
Last edited:
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
 
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...
 
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
 
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
 
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:
1762320086299.png


Other stuff working fine.
 
BE88u Alpha 2

VLAN page under LAN is broken. I can set a profile but the VLAN page itself doesn't load
Screenshot 2025-11-05 at 07.53.24.png

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

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