I thought I flashed 388.2 beta on my "facehugger edition" AX-6000, and thought it was working good, but then I realized it was just a dream. Carry on with all your testings! I have 0 input to contribute here!This is amazing feedback!
JUST flashed it and ALL working good?
I'm playing with 388_22525 and 388.2 beta for few days and found bugs that needed factory reset... but okay.
The "testing" you guys do reflects the quality of what you are going to get as a release. Go ahead. Sorry to interrupt.
This is amazing feedback!
JUST flashed it and ALL working good?
I'm playing with 388_22525 and 388.2 beta for few days and found bugs that needed factory reset... but okay.
The "testing" you guys do reflects the quality of what you are going to get as a release. Go ahead. Sorry to interrupt.
don't have time to test anything
facehugger edition" AX-6000
In reality, we all use our routers differently so a simple setup might report "All working good" which is nothing wrong with that. Those who run a more complicated setup might report otherwise. I'm glad his setup is working flawlessly!!!!This is amazing feedback!
JUST flashed it and ALL working good?
I'm playing with 388_22525 and 388.2 beta for few days and found bugs that needed factory reset... but okay.
The "testing" you guys do reflects the quality of what you are going to get as a release. Go ahead. Sorry to interrupt.
Perhaps a solution would be a regression testing checklist and @RMerlin can differentiate which features and settings were tested giving a better picture on what was tested.In reality, we all use our routers differently so a simple setup might report "All working good" which is nothing wrong with that. Those who run a more complicated setup might report otherwise. I'm glad his setup is working flawlessly!!!!
This is hilarious! Some relative newbie reports enthusiastically on his (I know, I'm assuming gender here) successful upgrade, and gets his butt kicked straight out of the gateThis is amazing feedback!
JUST flashed it and ALL working good?
I'm playing with 388_22525 and 388.2 beta for few days and found bugs that needed factory reset... but okay.
The "testing" you guys do reflects the quality of what you are going to get as a release. Go ahead. Sorry to interrupt.
All feedback is awesome...but it's still a one man show. Whatever makes this firmware better I'm all for it!Perhaps a solution would be a regression testing checklist and @RMerlin can differentiate which features and settings were tested giving a better picture on what was tested.
Out of all the firmwares, this firmware rocks. I think!All feedback is awesome...but it's still a one man show. Whatever makes this firmware better I'm all for it!
~~ I was collecting a list of not working right things and some of them unrecoverable without factory reset including in Asuswrt base ~~
Your approach is usually different than other's, but that doesn't mean to say it's wrong. In terms of sharing info within this forum, do you plan to post details in due course? e.g. "...list of not working right things..." and/or issues listed by device e.g. RT-AX86U / RT-AX86U Pro etc etc? That could / should / would be helpful to all.~~ this older RT-AX86U is the one with most reported issues lately. What I found happening in 388_22525 today may be model specific, but I couldn't recover with no factory reset and it happens every single time. I'm going to wait for about a week to see if someone notices the same thing in the new 388.2 beta ~~
Whatever makes this firmware better I'm all for it!
do you plan to post details in due course?
issues listed by device e.g. RT-AX86U / RT-AX86U Pro etc etc?
Should I still insmod md4 on startup?388.2 Beta 2 is now available for all supported models (except for the XT12, still no GPL for it). Changes since beta 1:
Code:639ff8e903 (HEAD -> master) Reformated recent changelog entries 2fb708f4c1 (origin/master) Updated documentation 7320eba6c1 curl: updated to 8.0.1 f92baff728 webui: replace method of renewing cert on DDNS page with Asus' new method used on the System page ae1ce59754 rc: only refresh DDNS on bound6()/deconfig6() events if IPv6 DDNS updates are enabled 413799a1aa openvpn: updated to 2.6.2 1253272632 webui: 5 GHz-2 Wireless Settings couldn't be saved on some models (issue introduced with 22525) ed51604f41 Add missing 386.9 and 386.10 changelogs 567a64f84c aaews: move to model-specific 82cb84e911 Bumped revision to beta 2
Yes. Broadcom decided to only include the module as an external module rather than built-in the kernel in the 5.04 SDK (and it's not enabled by default either, the build system enables the module during setup).Should I still insmod md4 on startup?
Wireless code is 100% Asus'. Closed source, I made no change to it.Also stock Asus fw does NOT let my clients associate at 6ghz. Asus should be ashamed a 1 person project is more reliable and stable than their army of engineers. They are a joke.
There's nothing for me to reconsider since I haven't made any decision...I hope you will reconsider...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!