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.5 alpha Build(s) ] available build(s)

Apply button is not working on Wireless - General page on multiple browsers (Chrome, Edge, Firefox) and was the only issue that I came across.

3006.102.5 fixed the issue where the SDN VLAN profile would default to the first entry in the drop down list when setting an access port.
The latest wireless driver seems to be working well without any particular issues.
Otherwise, most of the functionality seems quite stable on RT-BE96U.
 
Fine for me.
Must be a WiFi 7 issue...
It's a BCM4916 issue. Asus broke temperature reporting in the latest GPL, I need to backport the fix I had implemented in the RT-BE92U branch for 102.4 which already used the broken version of the code.

Apply button is not working on Wireless - General page on multiple browsers (Chrome, Edge, Firefox) and was the only issue that I came across.
Already mentionned in previous posts (and also already fixed on my end - bug introduced in the newer GPL).
 
Last edited:
I got still some "news" from my router...:

Jun 25 19:05:12 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 27 17:58:51 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 27 19:35:22 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 28 14:09:19 kernel: Oops: HOOK_PROLOG() is not used properly !?
 
After 24 hours with the updated WiFi driver, the connection has been very stable. The intermittent issues I experienced with version 3006.102.4 are no longer present. I haven’t noticed any difference between the 3006.102.4_beta and this newer driver, but so far, so good.
 
I got still some "news" from my router...:

Jun 25 19:05:12 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 27 17:58:51 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 27 19:35:22 kernel: Oops: HOOK_PROLOG() is not used properly !?
Jun 28 14:09:19 kernel: Oops: HOOK_PROLOG() is not used properly !?
QoS enabled..?
 
QoS enabled..?
Yes, it was enabled, although I certainly hadn't enabled it. With my bandwidth, it's unnecessary. Maybe it "came" with the update to alpha1?
It is disabled it now and I will observe it.

Thank you!
 
Almost 24hrs on my 3x units. All going very nicely from a family flogging & my home with business linked (VPN) operation. Usually average 50 clients active.
Edit-1: Found two quirks on this Alpha level. -->> Both AiMESH units RT-BE96U & GT-BE98 Pro loaded with "alpha1-gef34cb8940" the 2.4GHz & 5.0GHz Radios don't turn on, nor do their associated panel display lights. Only 6.0GHz bands enabled.
BTW: All wireless bands enabled on the main GT-BE98 Pro, just the AiMESH units lacking/missing the 2.4/5GHz bands.
Edit-2: On BE96U with ASUS code level: FW_RT_BE96U_300610237839 the wired backhaul flips to wireless connection. Replugged AiMesh 2.5Gb/s ethernet cable to BE96U
Edit-3. The cable re-plug didn't work, would flip to wireless connect after awhile. Rebooted the main GT-BE98 Pro and cable backhaul then worked ok on both RT-BE96U_3006_102.4_0 & FW_RT_BE96U_300610237839 after further & longer time testing with the different code levels.

Debug steps to get both AiMesh units, 2.5Gbp/s wired Back Haul connected, to get 2.4/5.0GHz bands operational again.
1st AiMESH unit: GT-BE98 Pro
- Did a "Hard Factory Reset on the BE98Pro. i.e. Power off, hold down WPS button, power on unit, when Power on light turns off after about 10secs, then power on.
- Add unit back into AiMESH config. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0GHz panel lights go from lit to unlit. Tried this twice, no success.
- Reboot the main BE98Pro (on alpha1) & then AiMESH BE98Pro (on alpha1) automagically connected back into AiMesh config, with 2.4/5.0GHz (& Lights) enabled.

2nd AiMESH unit RT-BE96U.
- Did a "Hard Factory Reset on the BE96U. i.e. Power off, hold down WPS button, power on unit, when Power on light turns off after about 10secs, then power on.
- Add unit back into AiMESH config. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0 panel lights go from lit to unlit. Tried this twice, no success.
- With BE9U in AiMesh config tried AiMesh "Remove Node" function & add then add BE96U back in. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0GHz panel lights go from lit to unlit. Tried this twice, no success
- Installed ASUS code level: FW_RT_BE96U_300610237839. Success.
- Installed merlin code level: alpha1-gef34cb8940. Failed.
- Installed merlin code level: RT-BE96U_3006_102.4_0. Success.
- Installed merlin code level: alpha1-gef34cb8940. Failed.
- Installed ASUS code level: FW_RT_BE96U_300610237839. Success. Have now stayed on this code level with the BE96U...need a drink though...lol.
Edit -2: More details. Noted later on with ASUS code level: FW_RT_BE96U_300610237839 the wired backhaul flips to wireless connection mode, of -73dbm. Then installed merlin code level RT-BE96U_3006_102.4_0, BE96U stays in wired backhaul mode.
Edit-3 as above. Reboot of main router GT-BE98 Pro fixed the wired backhaul on the BE96U flipping to wireless mode. The BE98 Pro didn't do this, it stayed solid on the cable back haul.

Now to have a serious drink or two!!
 
Last edited:
Running 30 hrs and no problems! I also noticed for the first time ever the memory used stays stable. All other firmware's would creep up 1-2 % per day.

CC
 
Last edited:
I have been traveling calmly across the internet lake with alpha1 for 7 days now!
Looking forward to seeing the beta launch.
 
Almost 24hrs on my 3x units. All going very nicely from a family flogging & my home with business linked (VPN) operation. Usually average 50 clients active.
Edit-1: Found two quirks on this Alpha level. -->> Both AiMESH units RT-BE96U & GT-BE98 Pro loaded with "alpha1-gef34cb8940" the 2.4GHz & 5.0GHz Radios don't turn on, nor do their associated panel display lights. Only 6.0GHz bands enabled.
BTW: All wireless bands enabled on the main GT-BE98 Pro, just the AiMESH units lacking/missing the 2.4/5GHz bands.
Edit-2: On BE96U with ASUS code level: FW_RT_BE96U_300610237839 the wired backhaul flips to wireless connection. Replugged AiMesh 2.5Gb/s ethernet cable to BE96U
Edit-3. The cable re-plug didn't work, would flip to wireless connect after awhile. Rebooted the main GT-BE98 Pro and cable backhaul then worked ok on both RT-BE96U_3006_102.4_0 & FW_RT_BE96U_300610237839 after further & longer time testing with the different code levels.

Debug steps to get both AiMesh units, 2.5Gbp/s wired Back Haul connected, to get 2.4/5.0GHz bands operational again.
1st AiMESH unit: GT-BE98 Pro
- Did a "Hard Factory Reset on the BE98Pro. i.e. Power off, hold down WPS button, power on unit, when Power on light turns off after about 10secs, then power on.
- Add unit back into AiMESH config. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0GHz panel lights go from lit to unlit. Tried this twice, no success.
- Reboot the main BE98Pro (on alpha1) & then AiMESH BE98Pro (on alpha1) automagically connected back into AiMesh config, with 2.4/5.0GHz (& Lights) enabled.

2nd AiMESH unit RT-BE96U.
- Did a "Hard Factory Reset on the BE96U. i.e. Power off, hold down WPS button, power on unit, when Power on light turns off after about 10secs, then power on.
- Add unit back into AiMESH config. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0 panel lights go from lit to unlit. Tried this twice, no success.
- With BE9U in AiMesh config tried AiMesh "Remove Node" function & add then add BE96U back in. After unit back into AiMesh, 60secs odd later, unit drops out. Unit's 2.4/5.0GHz panel lights go from lit to unlit. Tried this twice, no success
- Installed ASUS code level: FW_RT_BE96U_300610237839. Success.
- Installed merlin code level: alpha1-gef34cb8940. Failed.
- Installed merlin code level: RT-BE96U_3006_102.4_0. Success.
- Installed merlin code level: alpha1-gef34cb8940. Failed.
- Installed ASUS code level: FW_RT_BE96U_300610237839. Success. Have now stayed on this code level with the BE96U...need a drink though...lol.
Edit -2: More details. Noted later on with ASUS code level: FW_RT_BE96U_300610237839 the wired backhaul flips to wireless connection mode, of -73dbm. Then installed merlin code level RT-BE96U_3006_102.4_0, BE96U stays in wired backhaul mode.
Edit-3 as above. Reboot of main router GT-BE98 Pro fixed the wired backhaul on the BE96U flipping to wireless mode. The BE98 Pro didn't do this, it stayed solid on the cable back haul.

Now to have a serious drink or two!!
Did some more code load scenarios on the BE96U AiMESH unit after another reboot of the main GT-BE98Pro. This alpha1 code "gef34cb8940" does not enable 2.4/5GHz wireless or their LEDS on the BE96U. Code levels of RT-BE96U_3006_102.4_0 & FW_RT_BE96U_300610237839 work fine.
 

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