Recent content by sol1109

Should this update include a factory reset?

Just figured that out. Not the first time I misread 86U as 68U.

So I clicked on the flashing update icon from the main page and proceeded to install. But at the end it had installed 3.0.0.4.386_52062 which I see mentioned in another thread but not on the product page. I went to the Asus website and downloaded 3.0.0.4.386_52294 and tried several manual...

12 years is 5 years past the production run for most higher level chips.

Had mine since 2013. Went through several DLink routers before that in shorter times and hated dealing with problems and quirks. Been very happy with Asus but might give Synology a look.

After a day or so Core1 is down to under 30% so whatever was happening seems to have settled out.

A soft reboot via GUI did not. I noticed late last night after everyone went to bed that core 1 was down to the same levels as core 2. Today it is back up at 100%. I will try a power cycle tonight.

Just updated to this version. I am seeing core 1 staying at or near 100%. Don't recall this being the case before the update. Updated by clicking the flashing bell instead of a manual update.

What I am seeing in the log is a lot of Deauth_ind followed by Auth & Assoc for the same MAC address. In the below example I was watching YouTube on the smart TV when this occurred. Jun 30 07:38:25 syslog: wlceventd_proc_event(494): eth2: Deauth_ind MAC#, status: 0, reason: Deauthenticated...

Not sure how #40 and 41 (memory issues) apply to me. Anyway I did the factory default and reentered my settings. I still see WIFI occasionally drop off but have not been able to catch anything on the router end yet.

Since updating to this version my WiFi drops out several times a day. I will do a factory default and reenter setups as soon as I can get everyone off the network for an hour.

You will find memory status on the network map page / right status panel / status tab.

No, the system works fine it is just the webpage for the device that is hung.

I have encountered this issue for years over multiple software versions and not associated with any particular installation period. A power reboot always has solved it.