My router prompted me to install the firmware update in the title. Not ready to take a gamble, as the current firmware has been solid. Also, I can't see it on the support web site to learn what is in included in the update. Anyone give it a whirl yet?
I would do a clean reinstall of the router, sounds like some memory might be forked. Lots of instructions about how to do this, and then manually apply settings (do not restore from backup)
Could it be occuring when the IP lease renews (default is weekly I believe)? I've had issues with a few devices and had to assign them static IPs directly on the device
I just completed the reset, thank you for the guidance. CPU is sitting right around 70 degrees and everything else is working. Only weird thing was (1) the default IP address was 192.168.50.1, and (2) I lost my prior DDNS letsencrypt name and had to create a new one. NBD, very helpful forum.
I just upgraded my RT-AC86U to the beta firmware (letsencrypt wasn't working on the 384 firmware). Its running great, but checking CPU temp its right around 80C. Idid not do a reset, just a straight upgrade. Should I go through a reset to keep the CPU running cooler?
I've been running for an hour and none of those messages in the System Log. Perhaps they just aren't logging them, but hopefully they properly fixed it. I re-enabled AIProtection after the upgrade (don't use AIMesh)
I just rebooted one of my access points, which cleared the stats. With no device connected to 5gHz I show similar errors on the 5gHz service. Makes me think this might be a meaningless stat.
In case anyone else finds this thread, I updated to the newer firmware (came out a few days ago), and reset router after. Then imported backed up settings. Haven't seen the error message since. I'll keep an eye out, but hoping that fixed things.
Not sure I understand what you are asking. I can manage my access points remotely by the VPN I have on my router (was a Netgear R7000, but just upgraded to ASUS RT-AC86u). I juts connect via OpenVPN, then I can access the EAP225s via their IP addresses. Seems to be the safest way to do things...