wpte
Occasional Visitor
I'll just send it of to Asus thenRight, I don't have the know-how to investigate that type of crash.
I'll just send it of to Asus thenRight, I don't have the know-how to investigate that type of crash.
Hi Merlin, thanks for your great work. For me on a ac66u bandwith monitor (daily, per month) won't work. With older versions there were no problemes. Any ideas.
I do not confirm autorestart miniupnpd. Now must reboot manually. Do you need the syslog?miniupnpd gets restarted later down, so this doesn't cause any real problem. The first restart simply occurs just before the firewall gets reconfigured when a restart_net_and_phy event is issued (which pretty much restarts the whole networking stack).
I have seen this about 5-10% of the time as well. Others have reported it too. My router is the 68U@RMerlin
Today the below happened and can be replicated through multiple browsers on N66U
1.Login to router admin through
https://192.168.1.1:8443/Main_Login.asp
2. Instead of Router Admin (index page) only the below appears
(browser url is https://192.168.1.1:8443/ajax_coretmp.asp)
curr_coreTmp_2_raw = "52°C"; curr_coreTmp_2 = (curr_coreTmp_2_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_2_raw.replace("°C", "")); curr_coreTmp_5_raw = "disabled"; curr_coreTmp_5 = (curr_coreTmp_5_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_5_raw.replace("°C", "")); curr_coreTmp_cpu = "";
3. Router Admin page appears if you change the browser url to either of
the below (without the need to relogin)
https://192.168.1.1:8443/
https://192.168.1.1:8443/index.asp
I have seen this about 5-10% of the time as well. Others have reported it too. My router is the 68U
I use both radios...and I concur, issue first appeared in 380.65. The common thread with others has been with Firefox as the browser...you have experienced this with other browsers?
I use both radios...and I concur, issue first appeared in 380.65. The common thread with others has been with Firefox as the browser...you have experienced this with other browsers?
WOW!
#!/bin/sh
# force LAN port 4 to use the Guest Network for RT-AC66U
robocfg vlan 1 ports "1 2 3 8t"
robocfg vlan 10 ports "4 8t"
vconfig add eth0 10
ifconfig vlan10 up
brctl addif br0 vlan10
ebtables -t broute -I BROUTING -p IPv4 -i vlan10 --ip-dst 192.168.2.0/24 --ip-proto tcp -j DROP
ebtables -t filter -I FORWARD -i vlan10 -o ! eth0 -j DROP
ebtables -t filter -I FORWARD -i ! eth0 -o vlan10 -j DROP
Forum search did not turn up the issue reported earlier by you.
After your update went through this thread.
The culprit it seems are the certificates as mentioned earlier in this
thread by others.
Removed the keychain entries for 192.168.1.1 and also
Firefox ->Preferences -> Advanced->Certificates->View Certificates->Authorities
Firefox ->Preferences -> Advanced->Certificates->View Certificates->Others
Firefox ->Preferences -> Advanced->Certificates->View Certificates->Servers
Delete all references to 192.168.1.1 and carry out similar steps in
other browsers.
Clear Cache & Cookies etc.,
The issue which was happening everytime on router admin web login
did not appear again.
Firefox and other browsers web admin page load times has reduced too.
Will update the post if it happens in future.
1) Had no certs referencing Asus, Merlin, or 192.168.1.1.
2) Cleared cache and cookies
Seems fine for a day or two and then when I log in I get the temps page again. Just happened a few days ago and I cleared cache and cookies yesterday. This only started with 380.65 OR Firefox 51...this never happened before and now it's maybe 10%. Something is amiss.
I think I may have figured this out. I had a bookmark to access the 68U, http://192.168.1.1/Main_Login.asp. I can make the error happen EVERY TIME if I do not log out of the router, close the browser tab, open a new tab and then use my bookmark to access the router. Bam, back to the core temp readings. What seems to happen is that when logging out the router returns you to the Main_Login.asp screen. I can then close the tab, open a new tab and use the http://192.168.1.1/Main_Login.asp bookmark to get to the login screen...pressing login I get core temps about 10% of the time. What I think is happening in 380.65 is that it takes a longer time to actually log out of the system or the system thinks you are logged in...it's just slower than in versions prior to 380.65.
Regardless, I seemed to resolve the issue by editing my bookmark. Instead of going to http://192.168.1.1/Main_Login.asp, I changed the bookmark properties to just http://192.168.1.1. Seems to have resolved the issue but I will report back if it happens again.
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!