Router Slowdown
From DD-WRT Wiki
Revision as of 11:13, 19 February 2006 (edit) 82.228.206.193 (Talk) (Added problem symptoms) ← Previous diff |
Revision as of 11:17, 19 February 2006 (edit) (undo) 82.228.206.193 (Talk) (→Yet one more Solution - Corrected a typo.) Next diff → |
||
Line 56: | Line 56: | ||
=Yet one more Solution= | =Yet one more Solution= | ||
Apparently there is a bug in the WRT54GS v2.2 The bug involves a fatal memory access error due to a difference in the CPU clock speed | Apparently there is a bug in the WRT54GS v2.2 The bug involves a fatal memory access error due to a difference in the CPU clock speed | ||
- | and the clock speed on the memory bus. This bug causes connections to be dropped when transferring large files. New versions of the Linksys firmware overclock the CPU to 216 MHz. This can be fixed by logging into the router via SSH or Telnet ([[Telnet/SSH and the Command Line]]) | + | and the clock speed on the memory bus. This bug causes connections to be dropped when transferring large files. New versions of the Linksys firmware overclock the CPU to 216 MHz. This can be fixed by logging into the router via SSH or Telnet ([[Telnet/SSH and the Command Line]]) and executing the following commands. |
<pre> | <pre> |
Revision as of 11:17, 19 February 2006
Contents |
Introduction
A lot of people keep asking/telling that their router seems to slow down/crash/hangs/stops responding.
Usually these people are running P2P software like emule, bittorrent shareaza or something else.
You might want to play a little bit with the values, to fit it to your own needs.
Symptoms
Even if it happens the router doesn't answer pings anymore and no more http, you still can check what's going on through syslogd. Here is a brief description of what's going on :
- First, you'll see 'full, dropping packet.' messages followed by 'messages suppressed.'
- Eventually, it will get verbose and you'll see logs similar to the following :
<4>kernel: ip_conntrack: table full, dropping packet. <4>kernel: NET: 15 messages suppressed. <4>kernel: ip_conntrack: table full, dropping packet. <4>kernel: NET: 12 messages suppressed.
Solution
- Go to the Web-Admin and log in
- Go to 'Administration'
- Go to 'Management'
- Enter the following values at 'IP Filter Settings'
- Maximum Ports: 4096
- TCP Timeout (s): 90 or 120
- UDP Timeout (s): 90 or 120
Screenshot
Another Solution
DD-WRT has an inbuild proxy feature that allows rewriting of html content to filter activeX cookies etc. As this is load intense you may want to disable this feature. This should be done under
Security->Firewall
Unfortunately this function has 3 bugs
- Though all 4 checkboxes are unchecked the rewriting proxy is still running (you might have to reboot)
- It drops connections if under heavy load
- It probably runs haywire checking traffic on other ports than 80, hence the slowdown with p2p applications (unconfirmed)
The only solution is to totally disable the firewall (which I do NOT recommend) in
Security->Firewall
This fixes all slowdowns
This behavior has been seen in v22 and v23
Please report this to the maintainer and put it in the bug database
Yet one more Solution
Apparently there is a bug in the WRT54GS v2.2 The bug involves a fatal memory access error due to a difference in the CPU clock speed and the clock speed on the memory bus. This bug causes connections to be dropped when transferring large files. New versions of the Linksys firmware overclock the CPU to 216 MHz. This can be fixed by logging into the router via SSH or Telnet (Telnet/SSH and the Command Line) and executing the following commands.
nvram set clkfreq=216 nvram commit reboot