Insufficient ram
From DD-WRT Wiki
Revision as of 01:28, 16 July 2009 (edit) Phuzi0n (Talk | contribs) (New page: ==Introduction== Issues occur with routers that have only 8MB ram. DD-WRT includes several features even in micro builds but many of these features will cause the router to run out of ram ...) ← Previous diff |
Revision as of 01:59, 16 July 2009 (edit) (undo) Phuzi0n (Talk | contribs) Next diff → |
||
Line 7: | Line 7: | ||
* Not responding to ping | * Not responding to ping | ||
* Router crash or rebooting | * Router crash or rebooting | ||
+ | |||
+ | |||
+ | ==P2P Solution== | ||
+ | Copied from [[Router Slowdown]]. After you have rebooted and turned off any heavy P2P applications: | ||
+ | *Go to the Web Interface of the DD-WRT Device and log in | ||
+ | *Go to 'Administration' | ||
+ | *Go to 'Management' | ||
+ | *Enter the following values at 'IP Filter Settings' | ||
+ | **'''Maximum Ports''': 1024 | ||
+ | **'''TCP Timeout (s)''': 90 | ||
+ | **'''UDP Timeout (s)''': 90 | ||
+ | [[Image:Ipfiltersettings.JPG|alt IP Filter Settings at DD-WRT v23]] | ||
+ | ::Image: IP Filter Settings on DD-WRT v2.3 | ||
+ | *Save Settings and then Reboot Router | ||
+ | |||
+ | The above settings cause inactive TCP & UDP connections to be dropped after 90 seconds. | ||
+ | *If you start getting frequent disconnections from an Instant Messenger program bump your TCP timeout up to 300 first. | ||
+ | |||
+ | If you want about 15% more RAM available: | ||
+ | * First, make sure the [[CLI]] is enabled. This way, it is possible to connect to the DD-WRT Device and turn the Web Interface back on when needed. | ||
+ | * Then turn off the Web Interface. This is done through the Web Interface. Apply your changes. | ||
+ | * When starting the Web Interface on an as-needed basis, use the command 'httpd'. To close it later, use the command 'killall httpd'. | ||
+ | |||
+ | |||
+ | ==Other Solutions== | ||
+ | Due to the lack of RAM you must disable any non essential features. The common ram hogs that are disabled by default include: | ||
+ | *QoS - only the default rules will consume high ram. Custom created rules use negligible ram. | ||
+ | *Access Restrictions - only the default rules will consume high ram. Custom created rules use negligible ram. | ||
+ | *UPnP - This service makes port forwarding easier but not all programs support UPnP anyways. Custom created port forwarding rules use negligible ram. |
Revision as of 01:59, 16 July 2009
Introduction
Issues occur with routers that have only 8MB ram. DD-WRT includes several features even in micro builds but many of these features will cause the router to run out of ram on routers that only have 8MB ram. However, some devices that run micro builds have have more than 8MB ram; these devices should not easily run out of ram and can enable any of the included features.
These problems may occur directly after enabling a feature but often times may not occur until using the router with heavy P2P applications that cause the router to use ram that it normally wouldn't under low load. The router may only become 'slow' over time without crashing. Some symptoms can be:
- Slow web-interface, or cannot connect at all to web interface
- Slowing transfer of data, e.g. browsing, after a reboot
- Not responding to ping
- Router crash or rebooting
P2P Solution
Copied from Router Slowdown. After you have rebooted and turned off any heavy P2P applications:
- Go to the Web Interface of the DD-WRT Device and log in
- Go to 'Administration'
- Go to 'Management'
- Enter the following values at 'IP Filter Settings'
- Maximum Ports: 1024
- TCP Timeout (s): 90
- UDP Timeout (s): 90
- Image: IP Filter Settings on DD-WRT v2.3
- Save Settings and then Reboot Router
The above settings cause inactive TCP & UDP connections to be dropped after 90 seconds.
- If you start getting frequent disconnections from an Instant Messenger program bump your TCP timeout up to 300 first.
If you want about 15% more RAM available:
- First, make sure the CLI is enabled. This way, it is possible to connect to the DD-WRT Device and turn the Web Interface back on when needed.
- Then turn off the Web Interface. This is done through the Web Interface. Apply your changes.
- When starting the Web Interface on an as-needed basis, use the command 'httpd'. To close it later, use the command 'killall httpd'.
Other Solutions
Due to the lack of RAM you must disable any non essential features. The common ram hogs that are disabled by default include:
- QoS - only the default rules will consume high ram. Custom created rules use negligible ram.
- Access Restrictions - only the default rules will consume high ram. Custom created rules use negligible ram.
- UPnP - This service makes port forwarding easier but not all programs support UPnP anyways. Custom created port forwarding rules use negligible ram.