From Asus RT-N66U to Asus RT-AC86U 》Shakey Start...

[blue166]

Hi All,

I have been following these forums for hints and tips etc... for sometime but have only just registered as I would like to contribute and be part of the community.

I first got an ASUS router about 6 years ago after reading many good reviews for the N66U Dark Knight. I have to say it has been a fantastic router and can only think of one standard ASUS firmware that caused it any issues. CPU would go to 100% during little activity during this bad update. However ASUS did fix it in the next firmware so no huge panic. So Yeah it has been great to me and rock solid. I find it hard to almost to and replace it.

However, tech has changed. Demand in my house has grown with many more devices over time. Though the N66U has held up very well. So anyway with that said I decided to treat my network to a new router. I done a fair bit of research and seen that the ASUS RT-AC86U had good reviews and scores on a few sites.

So, I ordered one. Got it all set up and updated the firmware to the latest official ASUS firmware Version 3.0.0.4.384.45149. I believe that the router would have updated to the latest anyway?? Is this correct? 《 If the case I am not a huge fan of a firmware update automatically flashing without my approval. That is a big networking no no and I don't know why ASUS would force this on users. But someone please clarify that for me?

So I got the router set up in a basic config connected to my Openreach ECI modem same as my N66U has always been PPPOE etc... DDOS off none of the funky QOS or trend micro stuff on. Just as basic and light weight as I can get.

The Router lasted 7 days before crapping out and rebooting. So I gave it a going over and left it to run another 24hrs before introducing Merlins firmware. So the next day I downloaded 384.8_2. I didn't jump all the way to 384.9. May be I should have?

Anyway It took a few reboots and messing with system log to stop both CPUs rising to almost 100% 《 Is this a known issue? I have seen it mentioned in a few places and with different models aswell. Other than that the only other issue was 6 days in the Web GUI froze and I could no longer access it. Browser would just time out and not reach it. The Router continued to function just the Web GUI was now unable to be used. I left the router for another 24hrs and decided it bugged me to the point of introducing some network down time to reboot and leave my line off for a few hours. So done reboot with button. Pulled power cord out for 5 or so mins. Rebooted. Web GUI was back so that was good. The CPU thing started happening again so messed around with system log levels again and a couple of reboots. It then settled down again. Left it a few hours then turned modem back on this morning to establish internet connection again.

So all in all its been a shaky start with the 86U. And like I say this is coming from the N66U which was nothing short of a pleasure to use. I don't want to give up but I have come close I'll be honest.

I have since learned that the Web GUI does have a tendency to freeze and no longer give access on 384.8_2 but HTTPD crashes were resolved on 384.9?

I am still running 384.8_2 so I know the Web GUI will again fail in the coming days no doubt.

I notice some issues with dcd crashes on 384.9. Is this a crash that reboots the router or just a warning or sorts posted in log? I don't want to use any trend micro stuff at this time but have read it still causes dcd issues even with it all off.

Please can someone answer my questions. Sorry for so much in one post. Just want to make sure I can continue with this router as I am trying hard here.

Many thanks in advance.

 

[telUK]

I moved from the N66U to a AC86U a while back, the N66U was a solid router.

The AC86U is good as well, not had them issues you mention, only issue I have had with it is 5ghz dropping on the rare occasion, but I think I have solved that issue now.

Im on 384.8_2, I'm not certain but 384.9 looked like it had a patchy start with lots of people reporting issues, so I have never moved onto 384.9. Im going to wait for 384.10 which is currently in BETA.

Did you reset your router after moving from stock firmware to Merlins?

 

[blue166]

Hi @telUK

Thanks for the reply. Yeah I did a factory reset by holding in the pin button on the back of the device. Followed by some restarts with the physical button on back also. Is that ok? Is that the procedure?

I know the logs went mental with NTP logs to do with the time zone as I was setting it up offline so to speak. Guess nothing you can down about those logs? Would that be enough to cause the 2 CPUs to report a high load? Only thing I say I done wad change level of log reporting to warning and above and a couple of reboots calmed it.

Also what about this official ASUS firmware and automatic updates? Is this correct? As mentioned before that alarms me if the case and makes me cross with ASUS.

Of course I know the firmware is more optional on what to do with Merlins. Which is a plus in itself.

Also have you suffered the frozen UI in this version?

Many thanks,

 

[telUK]

I believe so, on Merlin firmware and I presume stock there is a tab in the web UI where you can reset the router also, so I do it like that.
I also use my ac86u connected to my VM router in modem mode, I haven't got a clue when it comes to all the logs and what it reports.
I have seen some mention about high cpu temps before, try a search on here see if you can find a cause.

As for the auto update, I have always been on Merlin firmware and I get a little yellow flashing caution sign in top right of web UI when a new update is available, so I presume its the same on stock and so should not auto update.

If you find you are still getting issues maybe try 384.9

 

[blue166]

Many thanks for the reply.

Yeah my old N66U used to have the flashing yellow icon to alert you of new firmware. It's only I read that the newer models auto update. Which I thought was very strange if true.

I will keep an eye on things. I will also keep an eye out for the new version of Merlins firmware. I guess it must be due soon?

 

[PeterV]

I moved from the N66U to a AC86U a while back, the N66U was a solid router.

The AC86U is good as well, not had them issues you mention, only issue I have had with it is 5ghz dropping on the rare occasion, but I think I have solved that issue now.

Can you share your experience ?

 

[roadwrenchtech]

I have noticed the client list and client map functions in gui are really clunky in the 86u I set up recently with latest factory firmware. It sometimes shows everything, others not and sometimes just a flash of what's missing. I use ubiquitis wifiman app for looking at what devices are on the network however the clunky gui made it more of a challenge than it should be to reserve ip addresses as I had to keep refreshing client list till they showed up then hop over to lan dhcp and add them before they disappeared again. Clients seem solid whether 86u shows them in list or not.

 

[blue166]

I have noticed the client list and client map functions in gui are really clunky in the 86u I set up recently with latest factory firmware. It sometimes shows everything, others not and sometimes just a flash of what's missing. I use ubiquitis wifiman app for looking at what devices are on the network however the clunky gui made it more of a challenge than it should be to reserve ip addresses as I had to keep refreshing client list till they showed up then hop over to lan dhcp and add them before they disappeared again. Clients seem solid whether 86u shows them in list or not.

So you are on the latest ASUS stock firmware?

How long is the uptime out of curiosity ?

Have you had any random reboots with the latest stock firmware?

 

[roadwrenchtech]

So you are on the latest ASUS stock firmware?

How long is the uptime out of curiosity ?

Have you had any random reboots with the latest stock firmware?

Yes, latest firmware at time of deployment which was around 10 days ago. It ran pretty well until a few days ago when it dumped most of the wifi clients. A reboot restored the missing clients. We did have an electrical storm around the same time of the issue though I found no evidence power had been off, but Im hoping it was an anomaly associated with the lightning and not the router wifi going down. Has performed solid since then. Time will tell.

 

[blue166]

Anyone else in regards to uptime with the 86U please?

My N66U i could leave up constantly it felt. Never had much need to reboot it. Infact I usually used to promt a reboot once in a blue moon just because I felt it needed it. The 86U doesn't give me that impression at this stage. Hope I am wrong mind you.

 

[L&LD]

Anyone else in regards to uptime with the 86U please?

My N66U i could leave up constantly it felt. Never had much need to reboot it. Infact I usually used to promt a reboot once in a blue moon just because I felt it needed it. The 86U doesn't give me that impression at this stage. Hope I am wrong mind you.

To have the most stable experience from your router/network as possible, I would suggest you do a full reset to factory defaults followed by a minimal and manual configuration of the router to secure it and connect to your ISP (see M&M Config link in my signature below). It wouldn't hurt to do a full 'sanitize' to your network either while you're at it. Seems it may have been a long while ago that that has happened and it may remove the last few glitches you may be seeing still.

I do a full M&M Config to a brand new router - even with one used with the as-shipped stock firmware. This greatly reduces or eliminates gremlins from being introduced to a working network.

There are many reasons for doing what I am suggesting and some of those reasons are listed in the links below.

If you want to give the RT-AC86U the best chance possible to give you superb performance along with stability and reliability too, I highly suggest following the steps I've outlined in the links below.

If there are issues still present afterward, then tracking down those remaining bugs should be more straightforward too.

From properly/fully resetting to factory defaults, using new SSID's, physically disconnecting the networking equipment and clients to dissipate static charge, to reset the network settings on handheld devices... what we're doing is giving a 'clean' playground for our new toy (in this case; the RT-AC86U) to play in.

No need to do this right now if your network is functioning to your satisfaction currently.

But, in a few days/weeks when RMerlin's 384.10 rolls out and is found to be stable, that might be the best time to do the above for your network.

 

[Dave Parker]

38 days and 16 hours here with no issues. Using Merlin 384.9 and mostly default settings.

 

[blue166]

To have the most stable experience from your router/network as possible, I would suggest you do a full reset to factory defaults followed by a minimal and manual configuration of the router to secure it and connect to your ISP (see M&M Config link in my signature below). It wouldn't hurt to do a full 'sanitize' to your network either while you're at it. Seems it may have been a long while ago that that has happened and it may remove the last few glitches you may be seeing still.

I do a full M&M Config to a brand new router - even with one used with the as-shipped stock firmware. This greatly reduces or eliminates gremlins from being introduced to a working network.

There are many reasons for doing what I am suggesting and some of those reasons are listed in the links below.

If you want to give the RT-AC86U the best chance possible to give you superb performance along with stability and reliability too, I highly suggest following the steps I've outlined in the links below.

If there are issues still present afterward, then tracking down those remaining bugs should be more straightforward too.

From properly/fully resetting to factory defaults, using new SSID's, physically disconnecting the networking equipment and clients to dissipate static charge, to reset the network settings on handheld devices... what we're doing is giving a 'clean' playground for our new toy (in this case; the RT-AC86U) to play in.

No need to do this right now if your network is functioning to your satisfaction currently.

But, in a few days/weeks when RMerlin's 384.10 rolls out and is found to be stable, that might be the best time to do the above for your network.

Appreciate the advice. I will certainly be reading through this.

 

[telUK]

Can you share your experience ?

Hi

In regards to 5ghz dropping, sure.

This may not be a fix, but as it stands since making these changes I have not had any issues.

I have followed the tips on these forums for disabling stuff like universal beamforming, airtime fairness but was still getting the occasional drop on 5ghz.

Someone else on here mentioned about changing the 5ghz bandwidth setting from Auto 20/40/80 to 80mhz and since then my 5ghz hasn't dropped, could just be luck though.

So try setting 5ghz bandwidth to 80mhz only.

I also changed my 5ghz channel to 100 at the same time so its hard to tell which one has improved things.

Only simple changes but they seem to have done the trick.