David Arnstein
Regular Contributor
I upgraded from ll.2 to 12.0 and I experience a regression. I am having a problem with web access to my router, when using https.
My router is an RT-AC68U, which I dirty-upgraded from 11.2 to 12.0 without incident. In the router's Administration|System page, I have set Local Access Config to Authentication method both, addresses http://192.168.1.1 and https://192.168.1.1:8443 .
Remote access via WAN is disabled. Enable access restrictions is disabled.
I only access the router from a wired ethernet port, LAN.
I can log in to the router OK as http://192.168.1.1.
If I log in via https://192.168.1.1:8443, Google Chrome indicates "Not secure." In the browser address bar, I see https: in red strikethrough typeface. Then ://192.168.1.1:8443.
If I log in via http://192.168.1.1:8443 using Mozilla Firefox, results are much worse. Firefox indicates it is VERY SLOWLY executing TLS handshakes again and again. Eventually, Firefox simply times out.
My router config is rather simple. No VPNs, nothing besides default routing and maybe 25 static host names in the DHCP config. 2.4 GHz and 5 GHZ WiFi are working, but I don't have any guest network. No cloud services or media servers.
I can access the router via ssh and run top. When the TLS handshaking problem happens, the CPU idle time is about 97%.
Any suggestions?
My router is an RT-AC68U, which I dirty-upgraded from 11.2 to 12.0 without incident. In the router's Administration|System page, I have set Local Access Config to Authentication method both, addresses http://192.168.1.1 and https://192.168.1.1:8443 .
Remote access via WAN is disabled. Enable access restrictions is disabled.
I only access the router from a wired ethernet port, LAN.
I can log in to the router OK as http://192.168.1.1.
If I log in via https://192.168.1.1:8443, Google Chrome indicates "Not secure." In the browser address bar, I see https: in red strikethrough typeface. Then ://192.168.1.1:8443.
If I log in via http://192.168.1.1:8443 using Mozilla Firefox, results are much worse. Firefox indicates it is VERY SLOWLY executing TLS handshakes again and again. Eventually, Firefox simply times out.
My router config is rather simple. No VPNs, nothing besides default routing and maybe 25 static host names in the DHCP config. 2.4 GHz and 5 GHZ WiFi are working, but I don't have any guest network. No cloud services or media servers.
I can access the router via ssh and run top. When the TLS handshaking problem happens, the CPU idle time is about 97%.
Any suggestions?