SoCalReviews
Very Senior Member
The horror@BreakingDad, shudder!
The horror@BreakingDad, shudder!
Imagine having a non-asus router.
Can you update without a full reset? Yes you can. Should you? That's a matter of opinion. I took every firmware update of Asuswrt on my AC66U_B1 for 2 1/2 years without doing a factory reset and never had a problem. When I finally flashed Merlin 384.19, I did the factory reset and realized it wasn't as big a task as I had imagined. Of course, I'm not running scripts and I use the default settings almost everywhere so my setup is pretty simple. FWIW, I updated from Merlin 384.19 to 386.1 without a factory reset and have not experienced any issues. YMMV.Just a small update! I have been running Merlin 386.1 for almost 3-4 weeks total runtime before I suffer a power outage due to storm so this router has been running pretty stable for me! Also this router seems to run cooler than all my previous router capping out around 68-72c.
I notice that there is an update for Merlin (386.1_2). What is the usual procedure for updating? Can I update without having to do a full reset every time I want to update? I know usually you should full reset for big updates but what about small update/revision of the same firmware
I notice that there is an update for Merlin (386.1_2). What is the usual procedure for updating? Can I update without having to do a full reset every time I want to update? I know usually you should full reset for big updates but what about small update/revision of the same firmware
Probably a good idea, especially since some of these early 386 releases had an issue with improperly setting up MTU values in nvram.do I have to factory reset after flash if i am coming from factory firmware 386_41535?
AX86U
Thank you.Probably a good idea, especially since some of these early 386 releases had an issue with improperly setting up MTU values in nvram.
Asus compile the RT-AX86U wireless driver with debug logging enabled. Just ignore those messages.@RMerlin upgrade went fine and I did factory reset after. I now have bunch of these messages in the log. is this expected?
Feb 17 21:17:10 kernel: CONSOLE: 020657.022 wl1: wlc_ampdu_recv_addba_resp: ae:88:22:71:4b:66: Failed. status 1 wsize 0 policy 0
Feb 17 21:17:16 kernel: CONSOLE: 020662.512 wl1: wlc_ampdu_recv_addba_resp: 74:d8:3e:c8:98:58: Failed. status 37 wsize 64 policy 1
My thoughts exactly. My pair of RT-AC86U are rock solid and do everything I need. I do not see me needing AX capabilities any time in the near future.I'm still impressed with the AC86U (had it since 2017). For example, our Virgin Media V6 box upstairs connects to the router downstairs over wireless with a consistent 1300/1300 link rate. I also disconnected and factory reset our AC68U mesh node and when I reconnected it as a node, that was also getting a 1300 link rate near the router.
The AX86U has got a lot to live up to, when the time comes to replace the AC86U.
You two sound like my Wife when I suggest not "upgrading, but updating" our current network, which has zero issues.
Stay Safe Everyone
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!