Recent content by mtrains

I am on 378.52 and for me Traffic Analyzer was causing this problem. Once I turned it off I have been running for 50+ days now without needing a reboot.

You might want to try turning off Traffic Analyzer if that feature is not important to you. I had similar issues and turning off Traffic Analyzer solved it for me.

My concern with Traffic Analyzer is memory usage. On 378.52, when I installed the firmware and reset everything the idle memory usage was around 63MB. After three days the memory usage had crept up to 105MB. When I turned off Traffic Analyzer and hit apply the memory usage immediately dropped...

Excellent build. On this build I could not reproduce the LAN crashes I saw on .50 and .51 under heavy file transfer load. The excessive RAM usage I saw in .51 is gone. In fact it is using less RAM now than it did on 376.49_5 which I went back to due to the problems I had in .51. The sporadic...

No, I am not using Plex media server. I am using all stock features. No custom scripts or custom/third party applications.

This happened to me also many times on 378.51. Went back to 376.49_5 with exactly the same setup and have had no issues for a week now. As I mentioned in one of my previous posts I suspect it is caused by the router running out of RAM space. But haven't had the time to look into it further.

There is something not right with DLNA in 378.51, mainly with discovery/connectivity. The DLNA server uses up a huge chunk of RAM also. I went back to 376.49_5 and DLNA is working fine with low RAM usage. I am going to stay there till this DLNA issue and memory usage issue is sorted out. I...

Has anyone noticed excessive RAM usage by the miniDLNA server in 378.51 and 378.50? On my system (AC68R) it is using around 100MB of RAM for about 500 mp3 files on the USB3 drive, which seems excessive to me considering the media server database is stored on disk. The problem I am running into...

I had the same issue on my AC68R. It happened twice last weekend. The only activity I had going at both times was a torrent download through a wired connection on one laptop and a YouTube video being viewed on another laptop (wireless). It happened to me once on 378.50_ta last week also...

Thanks John9527. I did not have have IGMP snooping enabled. But I did have UPnP enabled which I didn't want enabled. After I disabled UPnP on the router the DLNA discovery across the network is much more predictable. I don't know enough about UPnP multicast implementation to know whether...

I have noticed this too on my AC68R. DLNA discovery over the network has gotten flaky compared to the latest .49_4 build I was running on before. It is not as bad as it was in the early days of the RT68R firmware in the early part of last year. But it has definitely regressed in the .50 build.

These are normal. It happens when you try to access your HD after it has spun down due to inactivity. The HD spins up after these warnings are logged.

The LEDs turn back on if you restart the wireless. Any changes you make to your wireless settings or enabling/disabling guest wireless will restart wireless without rebooting the router. Restarting other services may also turn the LEDs back on. I haven't looked into what other services do this.

This just means your hard disk has spun down due to inactivity and you are now trying to access it. The system spins up the hard disk after this warning and everything works. It is a harmless message.

You can get around this problem by stopping the DLNA server before rebooting the router and then start the DLNA server manually after reboot. You don't need to delete any media. Yes, it is a pain in the neck but the workaround works.