• February 24, 2025, 07:10:33 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Work-around solution to prevent the need for frequent reboots.  (Read 7319 times)

mac

  • Level 1 Member
  • *
  • Posts: 11

Referring to these threads...


I have been able to determine the cause for the need to reboot my router every 24 hours.  It was obvious that the condition was related to a memory leak, but it wasn't obvious what type of activity was the cause or how to circumvent it.

Through some trial and error I have been able to determine that the resource leak is due to managed connections (or as D-Link refers to them, Internet Sessions).  If you are running an HTTP server or a file sharing client (like BitTorrent) you will see a lot of connections listed on the Internet Sessions page.  These connections are responsible for the resource leaks.

Although disabling your BitTorrent client (or limiting the number of permitted concurrent connections) and/or your HTTP server won't be a viable solution for everyone, it does seem that doing this allows the router to run for a long(er) period of time without performance degradation.

Hopefully this information will help someone.
Logged

jasoninaz

  • Level 1 Member
  • *
  • Posts: 12
Re: Work-around solution to prevent the need for frequent reboots.
« Reply #1 on: June 23, 2009, 11:19:45 PM »

Brilliant I'll be posting something about going back to 1.10b

Jasoninaz
Logged

memphis2k

  • Guest
Re: Work-around solution to prevent the need for frequent reboots.
« Reply #2 on: June 24, 2009, 02:25:59 PM »

Having upgraded to 1.11 or 1.10 but 1.01 seems pretty good.  Haven't ever restarted the router but if I do set BitTorrent (uTorrent) much higher than default settings, Digbsy (AIM & MSN) can't hold a solid connection.
Logged

mac

  • Level 1 Member
  • *
  • Posts: 11
Re: Work-around solution to prevent the need for frequent reboots.
« Reply #3 on: June 24, 2009, 03:07:51 PM »

Having upgraded to 1.11 or 1.10 but 1.01 seems pretty good.  Haven't ever restarted the router but if I do set BitTorrent (uTorrent) much higher than default settings, Digbsy (AIM & MSN) can't hold a solid connection.

The memory leak issue seems to have been introduced by the 1.1x firmware.  I did not have problems prior to the update.
Logged

terrydiehard

  • Level 1 Member
  • *
  • Posts: 7
Re: Work-around solution to prevent the need for frequent reboots.
« Reply #4 on: February 16, 2010, 09:17:26 AM »

I own the Dir-825, hardware version A. When I got the item with firmware 1.01, connections dropped tremendously. I upgraded to firmware 1.11NA so as to solve the problem but this made it even worse. Connections dropped even more and other persons were complaining since they also shared the internet connection via the router. I always had to keep on physically powering off the router and plugging it back on. It got so bad that I installed an electrical switch on the plug that connected the router to an electrical outlet. So instead of pulling out the router's charger and then plugging it back on so as to reboot the router, I could now switch off the power supply.

However it has been a week and a half thus far and I have not had to reset the router. This is of course a world record for me since I had to reset this router every 2 days or so. I'm not sure if it's a fluke or what but I'll tell you what I did. I first saved the router settings to my hard drive. Then I upgraded the router's firmware to version 1.12NA. Then I upgraded to firmware version to 1.13NA right after.I then reloaded the router's settings that I saved on my hard drive. In the advanced tab of the router's webpage I went into the Qos settings. I unticked "Automatic Upload Speed" and I set the manual uplink speed to 360 kbps. My acutal uplink speed is 256 kbps but I just set the uplink a little higher to see what would be the effect. Thus far there has been no ill effect of doing such. In the end the router has not dropped connections or stopped being accessible via it's webpage. So I guess you can try this so as to prevent frequent reboots.

However I don't know if things will go worse in the third week or so. I'll see and hopefully post an update.
I've given up on shareport since my main issue was the router dropping connections and being inaccessible via it's webpage.
Logged