D
Deleted member 22229
Guest
I have used the fork since the day it came out all versions on both my N66U and my AC68U and never had any issues you describe. Perhaps something in your environment.
My RT-N66U spontaneously reboots 1-3 times each day, and has been doing so for the last several versions of The Fork.
I have been capturing syslogs to an external drive, but there is absolutely nothing showing - just normal activity and then a sudden reboot.
I have a very vanilla setup; no USB servers, no parental control, no QoS, no VPN, no AiCloud, no optware or entware. For me, it's just a router. I am using both 2.4 and 5 GHz bands.
Does anyone have any experience dealing with an apparently symptomless series of reboots? And found a cure? I'm happy to provide further information on request.
My RT-N66U spontaneously reboots 1-3 times each day, and has been doing so for the last several versions of The Fork.
I will have to look around for an equivalent power supply. Jiggling the wire doesn't do anything.I don't believe there are any other reports like this, so here are a couple of things I'd check....
- Do you have another power supply that you could try? I've seen more that one occasion where those 'wall warts' have become flakey.
It feels fine. Just now may have been the first time I've touched it since I installed the router.- If you work the power switch on the router, does it 'feel' right? There have been reports of the switch breaking and it could be on the edge.
This is a possibility. The router's in a closed closet near a UPS which runs warm. Ambient temp is 82 F. Radio temps are 57/60 C or 136/138 F.- How is the temperature reported by the router? Is it in an enclosed area where it could be overheating?
The modem is rock solid, having been up for 54 days with no unusual events.- Have you logged into the modem to check if there are any strange events logged? How are the power levels for your connection as reported by the modem?
I can't say. I only started noticing the reboots the past few weeks. The router reboots quickly enough that most of the time, the reboots go unnoticed if no one is actively using the network. So I'm not even sure how long this has been going on.I am a few versions back, what was the last good version for you?
I can't say. I only started noticing the reboots the past few weeks. The router reboots quickly enough that most of the time, the reboots go unnoticed if no one is actively using the network. ...
cat /tmp/syslog.log | grep -i -e "login" -e "password" -e "Exit"
Protecting Yourself as a Consumer
As we have seen above the router DNS hijacking malware is taking advantage of default credentials on the routers, and bugs that allow unauthenticated configuration requests to be sent to the routers. The best protection available is to ensure the firmware on your router is fully patched, and to change the default credentials.
I read about this vulnerable one the other sources and there was comments, that people was affected even if they change they default credentials. That is the reason why I asked.If you give your router a non-default password, you should be safe.
Well, I notice them now that I'm looking for them. I just meant that in normal use, unless someone in the house is actively doing something which wants to move bits through the router, reboots can go unnoticed.I would notice a reboot because I run this command
touch $MOUNT_PT/Logs/router.log
echo '**************** ROUTER REBOOTED! ********************' >> $MOUNT_PT/Logs/router.log
tail -n +1 -f -s 1 /tmp/syslog.log >> $MOUNT_PT/Logs/router.log 2>&1 &
I was reading another post which reminded me....there have been problems in the past when both ipv6 and NAT acceleration are active on some ISPs (and the way the ISPs are still tweaking ipv6 that can change over time). Have you tried to disable either one and see if that helps?I can't say. I only started noticing the reboots the past few weeks
Yeah, I stumbled across that post also. I am now trying NAT acceleration off. One tweak at a time...I was reading another post which reminded me....there have been problems in the past when both ipv6 and NAT acceleration are active on some ISPs (and the way the ISPs are still tweaking ipv6 that can change over time). Have you tried to disable either one and see if that helps?
And BTW I got strange activity with Asus DDNS service: http://cl.ly/image/1w1M1K3c0L0z http://cl.ly/image/30313k0G1614 http://cl.ly/image/2C0l1b260A0L I run 10E on RT-AC68U.
I haven't seen any of that. What do you see when you go to WAN - DDNS in the router?
Same on my RT-N66U , no reboot since 10E1 update 3 days agoSome of you guys mentioning reboots, i can't say I have noticed any reboots on my n66u on version 10.
Looking in system log uptime is 5 days 22 hours, I take it that would change if I rebooted or the router kept rebooting?
Cheers
I'm also having this problem with the Asus DDNS service. Updated my N66U from V7 to V10, had to reset to factory default, and then restore settings. I got both of these messages last night. Tried again just now, and it finally connected after a couple of tries.I read about this vulnerable one the other sources and there was comments, that people was affected even if they change they default credentials. That is the reason why I asked.
And BTW I got strange activity with Asus DDNS service: http://cl.ly/image/1w1M1K3c0L0z http://cl.ly/image/30313k0G1614 http://cl.ly/image/2C0l1b260A0L I run 10E on RT-AC68U.
I won't rule out a problem, as integrating the Custom DDNS script support turned out to be more of a pain than I expected. But, I spent last evening going thru the code and nothing jumped out at me....if it's a bug, it's subtle. That error message is only a translation of an HTTP 401 response (bad authorization/logon credentials), so it may be a problem on Asus side. Give it a day and see if it works itself out.I'm also having this problem with the Asus DDNS service. Updated my N66U from V7 to V10, had to reset to factory default, and then restore settings. I got both of these messages last night. Tried again just now, and it finally connected after a couple of tries.
I'll monitor it over the next while and post back if it hasn't worked itself out. (Temporary problem with Asus DDNS?)
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!