Wireless crawled, then couldn't access UI on RT-N66U w/ .40

[binarydad]

Not sure what happened, but I decided to update all 6 of my windows 8.1 machines at once , so there was a bit of network traffic and a few machines rebooting. All of a sudden, wifi came to a crawl, then picked back up, then noticed I couldn't get to the UI - it just hung as it tried to connect. LAN speed was fine. Wireless wasn't at max capacity. It's almost as it I crippled it.

A reboot fixed it. I never noticed this before. Has this happened to anyone else?

 

[thelonelycoder]

Probably overloaded. Have you saved or looked at the routers log?

 

[binarydad]

No. The only log I'm aware of was cleared when I did a restart. I'm not familiar with other forms of logging to a file on this thing.

 

[thelonelycoder]

In /tmp/ you'll find syslog.log as the current log.
There may also be a syslog.log-1 file. This is the older syslog.log file saved automatically.

 

[thelonelycoder]

Sorry, syslog.log-1 does not survive a reboot. My bad for not checking before posting.

 

[thelonelycoder]

You could save the logs to /tmp/mnt/sda1/tmp by adding a script (old files are deleted after 2 days):
/jffs/scripts/copylog.sh

#!/bin/sh
logfiles=`ls -1 /tmp/*.log*` # find log files in tmp
for xx in $logfiles
do
    name=`echo $xx|cut -d. -f1,2`
    datetime=`date '+%Y%m%d%H%M'`
    cp $xx /tmp/mnt/sda1/$name.$datetime.log
    find /tmp/mnt/sda1/tmp -mtime +2 -type f -delete # delete files older than 2 days
done

And make it executable

chmod a+rx /jffs/scripts/copylog.sh

Then add a cron job to run it every 10 minutes:
add to /jffs/scripts/services-start

cru a CopyLogs "*/10 * * * * /jffs/scripts/copylog.sh"

Make sure the /tmp/ directory exists on your Stick.
And then reboot

 

[jamestx10]

I have not had Wireless slow to a crawl, but I do lose access to the GUI after several days of uptime.

 

[nmt1900]

Actually it has happened few times - and 374.40 is first release that has been causing any problems until now.

Reset and reconfiguration (no resets for a quite many upgrades) did not help. Went back to 374.39 and problem disappeared.