I assume you have refreshed the browser cache.On Chrome (or Edge, or IE for that matter) the Wireless page is not showing all the trimmings around the outside of the main wireless settings panel.
Makes setting up Wireless kinda hard...
On the home page, the System Status section seems to be missing the tabs it used to have, the key field is blank, the LAN IP, PIN code, LAN MAC address, and both wireless MAC addresses are all blank/show no data.
Anybody else seen this? Any workaround? Any likelihood of a remediation from ASUS anytime soon?
On Chrome (or Edge, or IE for that matter) the Wireless page is not showing all the trimmings around the outside of the main wireless settings panel.
Makes setting up Wireless kinda hard...
On the home page, the System Status section seems to be missing the tabs it used to have, the key field is blank, the LAN IP, PIN code, LAN MAC address, and both wireless MAC addresses are all blank/show no data.
Anybody else seen this? Any workaround? Any likelihood of a remediation from ASUS anytime soon?
Yes, I've flushed Chrome's cache and tried alternate browsers/platforms that don't usually administer the router.I assume you have refreshed the browser cache.
I suggest to revert to Factory defaults and manual configure the router again.
Hi wouterv,I am glad my router is not unique
These system log entries appear after the GUI crash as result of opening the System Status > Status Tab:
The GUI crash happens in both latest versions of Firefox and Edge.Code:Dec 4 19:38:47 watchdog: restart httpd Dec 4 19:38:47 rc_service: watchdog 277:notify_rc stop_httpd Dec 4 19:38:47 rc_service: watchdog 277:notify_rc start_httpd Dec 4 19:38:47 RT-AC68U: start httpd
All the rest the router is stable with performance as before.
Anyway I am surprised with RMerlin, that peopke like you still see need for SSID, passphrases or hostnames with odd characters while it adds zero value.Clearly they have problems dealing with otherwise perfectly legal PSKs. They operate the WiFi with them fine but the GUI gags up. Properly encoding strings of arbitrary characters is HTML 101.
Rather than re-key dozens of devices that use the existing key, I found a workaround to these ASUS bugs: I created a 64hex key from the ASCII and the SSID using an available encoder on the web. Works a dream. I edited the nvram-save file to replace the string PSK with the hex one. Restore Factory. nvram-restore the modified backup. Works a dream. The broken ASUS GUI is happy. The client devices are happy.
Thanks @RMerlin for all you do for this community.
Thanks! I now also know why it worked at first, with a laptop still hardwired for the firmware upgrade:Hi wouterv,
Just wanted to let you know in Merlin’s 382.2 beta 1 release this crash is fixed.
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!