Reading is fundamental...
don't mean to step on any toes here but i took the dive from the stable release (45717) to 81352. so far no issues. in fact, my connecteds seem to be running quicker. i can categorically state that i'm much quicker by 20% while using vpn.
the only thing that i have noticed is a very high cpu usage. cores are between 95% and max with 2 tvs streaming. if 1 tv, only 1 core seems to be maxed.
it's only been about 72 hours on this new release. did the gui install with no reset at all.
i'd appreciate any an all thoughts from u experts.
don't mean to step on any toes here but i took the dive from the stable release (45717) to 81352. so far no issues. in fact, my connecteds seem to be running quicker. i can categorically state that i'm much quicker by 20% while using vpn.
the only thing that i have noticed is a very high cpu usage. cores are between 95% and max with 2 tvs streaming. if 1 tv, only 1 core seems to be maxed.
it's only been about 72 hours on this new release. did the gui install with no reset at all.
i'd appreciate any an all thoughts from u experts.
thanks guys (atlga/ozarkedge), great feedback!
i'll go ahead and do the full reset now. haven't done as much in years.
huge difference!!This FAQ explains the reset to factory defaults. Since it's been years, you need to read it. It will caution you to not restore saved settings... to reconfigure from scratch. I would do the webUI Restore w/Initialize for a fuller purge... they call it Restore in the webUI... it's the same as the button reset except you can't do the Initialize with the button reset.
There may be other reset tricks, some historical, mentioned here, but I've never done more than the obvious ones... the button reset or the webUI Restore reset w/Initialize.
Removing an AiMesh node automatically resets it... which is convenient.
Feel free to reset a few times and to cycle power OFF/wait.../ON before proceeding to re-configure.
OE
huge difference!!
did all that you mentioned very likely while you were responding. the cores barely hit 1% now, even while streaming youtubeTV. ram is a more respectable 64%. it was way past time. i'm now a reset believer. gotta hope this update is more stable than than the venerable 45717. so far so good though being up solid since 3/13 even with the issues. i am seeing faster connects with a couple devices.
. . . again, many thanks to you and all
I've stayed on 45717 for quite some time because in my 2x RT-AC86U airmesh setup all other versions have given my droputs in network traffic every 5 minutes or so - which makes online meetings or gaming impossible.
Unfortunately 81352 shows the same bad behavior and I regret I upgraded (yes i did reset both units post upgrade) - is there any settings to check for good wifi performance before i install 45717 again….
No its the Wifi which is instable - I have 2 SSID one 2.4 and one 5 and it works super on the older firmareSeems strange that you are experiencing 'dropouts'. Even when wired to the router?
OE
No its the Wifi which is instable - I have 2 SSID one 2.4 and one 5 and it works super on the older firmare
First off, I am not normally a forum poster. I however felt obliged to create an account to say THANK YOU to the many on this forum who have helped me with issues over the past year. Merlin,
Ozark, L&LD, Val, and many more whom I apologize to for not mentioning. You are not being paid enough that is for sure!
With that said the 86u was my first Asus router and I must say I struggled with the device. I am a software engineer by trade, so I love breaking things down, trying new ways with old methods, etc. I must have installed 100 different combinations of firmware on the 86u this past year. I followed L's M&M configs so many times, I have them memorized! I can honestly state that the 5717 firmware for the 86u is the most stable.
Now to the good stuff. If this is posted in the wrong place, please let me know.
Your mileage may vary but I was able to get the new 81352 firmware rock solid stable while at the same time using AI protection, Smart Connect, Qos, Beamforming, etc. Here are the steps:
1) Nuclear Reset using L's directions
2) Install 5717 and set up router the way you want
3) Firmware upgrade under the Administration tab. DO NOT reset or go nuclear.
4) Once complete, press button on router and unplug. Leave off for 1 minuter. Restart.
I know this sounds way too easy, but I believe 5717 as the backbone to any firmware update was essential in my testing. You will still get the WLC Events, but if you are not using Merlin, then just ssh into router and set the nvram logging to 5. Even Roaming Assistant is rock solid.
Again, thank you so much for your hard work!
Now if someone could help me set up my Alias!!!
Other than multiple drop outs from time to time my router performs decently on 81352 . Its been a long time since i used 45717 so i cant compare but id say stay on latest firmware and when there is drop out just manually restart router it should help.
Interesting. I would appreciate any @RMerlin reflections on this method approach as he would better know what's taking place inside the router, if anything special.
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!