Yes. I download the latest from Intel website.my ax200 connects fine to 5GHz on my AX88 with 384.19. do you have latest drivers on the ax200?
Yes. I download the latest from Intel website.my ax200 connects fine to 5GHz on my AX88 with 384.19. do you have latest drivers on the ax200?
Yes. I use the latest driver as you pointed.Make sure you load the latest driver from Intel. Intel fixed some reconnect issues with this release:
21.90.3
This is how all over the place the current firmware + GPL release situation is, as of tonight:
https://docs.google.com/spreadsheet...Xq4I0i6lQo-RN48SGFSkKNKq8/edit#gid=2007755387
I can't deal anymore with the complete mess that 384 releases have become on Asus's end, with some GPLs being 4+ months outdated, only two models out of 10 sharing the same release, two models not even having recent enough GPLs to be compatible with every other models, etc...
I'm done with firmware releases until Asus re-unifies everything and starts issuing more regular GPL releases, which most likely won't be happening until everything is moved to the 386 code base. So, next release might be 3 months from now, 6 months from now, a year from now? I don't know, but it will take whatever time it takes. I'm tired of trying to mix and match all of these separate releases, and dealing with the aftermath.
So until then, run whatever works for you, be it 384.19, 384.18 or Asus's stock. It's out of my control, and I simply give up trying to keep it all together in the current situation.
what are your settings on the 5GHz wireless config page?Yes. I use the latest driver as you pointed.
I re-formatted USB drive and JFFS this morning, re-installed scripts, started from scratch with everything but resetting the router. That will be my next step, if any. All is clean from the USB up, and everything seems to be smooth now. Only took a couple of hours, and I felt like I would continue having problems if I didn't. There must have been something corrupt about my JFFS backup, because I reformated it (after I figured out to hit the RESET button at the bottom) and uploaded it and had problems until now. Now my RAM allocation is back to 92%, and my head is empty. Only thing I lack is configuring the NTPmerlin servers, I think.Definitely all the issues you've posted on the forum recently look like JFFS corruption which is a known issue on 384.19 + AC86U.
You needed to have done the JFFS backup thingy as per the firmware installation instructions ... if you didn't, you are going to have to wipe your JFFS partition and start over, otherwise you'll just get more and more JFFS corruption as time goes on, and it will cause issues with your custom scripts etc....
After reading all pages, two things were mentioned which concern me.
a) if you change the default login userid from admin to something else, you may get burned somewhere in this "format and then restore JFFS after flashing to 384.19" process. It seems no matter what we do, we should "restore the JFFS backup" period. I think @L&LD made that clear! TY!
So before we do this 384.19 on an AC86U, should the recommendation be: "If you have changed the router's login ID from admin to something else, change it back to "admin" before updating 384.19" ??
b) With all the JFFS issues with 384.19 + AC86U.... I feel like I want to get a spare AC86 testing router and practice the upgrade on it first. Since I've never done that, if I backup the router's config in the GUI and the JFFS in the GUI, can I then restore them to a different AC86U? Will all the router's setups carry over with those 2 items restored?
You needed to have done the JFFS backup thingy as per the firmware installation instructions ... if you didn't, you are going to have to wipe your JFFS partition and start over, otherwise you'll just get more and more JFFS corruption as time goes on, and it will cause issues with your custom scripts etc....
Actually the latest are 21.110.1... but for some reason Intel took down the customer version and only left the IT oneMake sure you load the latest driver from Intel. Intel fixed some reconnect issues with this release:
21.90.3
Does anyone know if this latest version has these vulnerabilities patched for the RT-AC3100?
View attachment 25589
check the Changelog please!
Some cellular providers (I'm looking at you Verizon) specifically force phones on their network NOT to use WiFi calling if there is a cellular signal, no matter how poor. The phones will drop calls repeatedly or cut out parts of conversations rather than use your WiFi. In Android 7 you could force Verizon phones to use WiFi calling with a little ADB 'hack' which is why I have spent three years dismissing several alerts a day asking me to update my version of Android.
Restore your backup headand my head is empty.
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!