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!

Beta Asuswrt-Merlin 3006.102.5 Beta is now available

Ah, a misunderstanding from the previous posts then.
I created a post on how to tell if drivers have changed.
Just because the date changes does not mean a newer driver you also have to look at the driver version number.

 
Not true or it would have been in the release notes.
The driver is included with the GPL. I have no idea if a given GPL has a newer driver or not. So, it won't be in the changelog, unless I had manually changed it myself.
 
Is there a way to disable the new login password requirement? I feel that 10 characters with one upper case letter, a special character and no repeating characters a bit much for access within a home LAN!
 
Is there a way to disable the new login password requirement? I feel that 10 characters with one upper case letter, a special character and no repeating characters a bit much for access within a home LAN!
I use 30 hexadecimal characters... 😁
 
Last edited:
The driver is included with the GPL. I have no idea if a given GPL has a newer driver or not. So, it won't be in the changelog, unless I had manually changed it myself.
Just out of curiosity, the disappearance of AMPDU optimization inside Wireless Professional.
Any idea of what happened? Seems to be mixed opinions on that option.
Most likely Asus doing it. But just in case you have a theory or know anything 🙂

FlexQoS totally wrecking the router on this update... Is this something for the FlexQoS devs?
I'm not sure in how I can do anything to gather info on this issue.
Might be a lower level of diagnostic I can't do.
 
I also thought it was a display issue, so I did some more testing:

On the 'Double WAN' page, I selected the '2.5Gbit LAN 1' as internet port.
The I unplugged everything and plugged the internet cable into LAN1.
NO INTERNET!

I also messed around with double wan - same result. My conclusion is:

There's no way you can use any LAN ports for internet access!

So this is something deep down in the firmware. I can't believe Asus haven't tested such a basic thing but instead relies on us to test their firmware. They really SHOULD have a testing suite to catch things like this.

Edit:
Reverted to 3006.102.4, now 2.5Gbit LAN port can work as internet port (auto detection), think I will stay here.
On my RT-AX88U_Pro I can successfully select any LAN port for WAN access (enabled Dual Wan, change primary to LANX and secondary to WAN, move WAN cable to LANX and works fine).
 
FlexQoS totally wrecking the router on this update... Is this something for the FlexQoS devs?
From memory, FlexQoS relies on Adaptive QoS which is broken.
 
Is there a way to disable the new login password requirement?
No. Password/login management is closed source.
Just out of curiosity, the disappearance of AMPDU optimization inside Wireless Professional.
Might be hardcoded based on other settings. Might be a setting that never worked or had no effect when changed. I don't know.
No one should be running FlexQoS on a BE router.
Maybe it's time to add a check to FlexQoS since I have reasons to believe that Adaptive QoS as people know it isn't coming back for Wifi 7 (I do know of their other plans that would most likely replace it tho, nothing has been publicly announced yet). Check the rc_support nvram for the presence of "wifi7" in it, and warn users that it's not compatible.
 
From memory, FlexQoS relies on Adaptive QoS which is broken.
Not really sure in what way Adaptive QoS is broken though.
If whatever that is broken got fixed, that means FlexQoS could work again, right?

Anyways... If Adaptive QoS won't return on BE routers in the previous shape, nor FlexQoS would ever work... And especially now when it it even "kills" the router if you install it, then it would be a good idea to not only inform but to prevent it from installing to begin with.
 
No one should be running FlexQoS on a BE router.
Personally had it for testing, if it would ever come back and work as intended again, I'd notice it.

However, not even booting to a otherwise functional state, or letting the user access the router is a new thing with the new firmware.
 
I have reasons to believe that Adaptive QoS as people know it isn't coming back for Wifi 7 (I do know of their other plans that would most likely replace it tho, nothing has been publicly announced yet)
I wonder if they’re going to do more with this DNS Intercept dnsqd feature that I noticed runs on WiFi7 devices. It seems to be aware of many domains like the old bwdpi categories.
Check the rc_support nvram for the presence of "wifi7" in it, and warn users that it's not compatible.
FlexQoS is now under the AMTM-OSR umbrella. All are welcome to submit pull requests to their repo. I surrendered all my commit rights.
 
And especially now when it it even "kills" the router if you install it
However, not even booting to an otherwise functional state, or letting the user access the router is a new thing with the new firmware.
You’re the first victim. Are there any useful logs remaining from the murder of your router?

You can share them here:
 
Last edited:
Is there a way to disable the new login password requirement? I feel that 10 characters with one upper case letter, a special character and no repeating characters a bit much for access within a home LAN!
Solution: flash 3006.102.4-configure-save backup of system and JFFS then flash 3006.102.5 (beta or final). Old user and password retained.
Job done!

(@MDM - 30 hexadecimal characters? And you write that down somewhere?)
 
(@MDM - 30 hexadecimal characters? And you write that down somewhere?)
Yes of course, there is no chance remembering it (and that is the point)! Saved in the browsers and app, and text on cloud (all behind same passwords and 2FA, PIN and passkeys). Newer had issues of being hacked...
Since that router password depending of setup is not jut LAN accessible (and even that is risky, since someone could break into your WiFi and voila LAN access - so I even limit the devices that can access the router settings) it is important to be as complex as possible to be on the safe side.

Same for all my passwords, web, app, bank... 20-30 random hexadecimal characters, 2FA, PIN and passkeys minimum.
 
You’re the first victim. Are there any useful logs remaining from the murder of your router?

You can share them here:
I don't really know how to fetch any info of value, since everything is locked out at that stage. I would assume that most data is internally on the router, and at best I only reach the login window for a very brief moment. So a full factory reset and wipe of SSD to set up from scratch has been done (twice). I can see it try stuff and eventually reboot of its own if waiting long enough.
So extract valuable info might be tricky. I can go over there to mention the problem at least. The script must be poking at a sore point, starting with this update. Not sure what I can do to help neither the script or the update itself due to the type of failure.

I'm only happy it happened during my vacation, so there was plenty of time to spare :) Less time to play when work starts again.
 
"Apply" button in wireless page is still not working (GT-AX6000 AiMeshed with a single XT9)
Reported in 102.4, reported in 102.5 alpha, reported in 102.5 beta... and i'm not the only one
Evidently this is not a bug... but no one gave us this anwser (or an answer, at least, at all)
The only workaround is to delete AiMesh, make wireless change, and rebuild the AiMesh. I don't this this is the way it's supposed to work
 
"Apply" button in wireless page is still not working (GT-AX6000 AiMeshed with a single XT9)
Reported in 102.4, reported in 102.5 alpha, reported in 102.5 beta... and i'm not the only one
Evidently this is not a bug... but no one gave us this anwser (or an answer, at least, at all)
The only workaround is to delete AiMesh, make wireless change, and rebuild the AiMesh. I don't this this is the way it's supposed to work
The other reports of similar issues in the 102.5 alpha were all different issues introduced by the new GPL merge, and they were all fixed before the beta release.


I am unable to reproduce your specific issue. What's the browser console error message, and what's on the line where the error occurs?
 
Is there a way to disable the new login password requirement? I feel that 10 characters with one upper case letter, a special character and no repeating characters a bit much for access within a home LAN!
Interesting. On my GT-BE98 Pro, I’m using a 7 letter password. No numbers. No special. Only accessible via LAN. I’ve never used any special characters or numbers albeit Merlin 3006.102.4.
 

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