Router Slowdown

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 02:33, 22 January 2006 (edit)
84.129.241.214 (Talk)

← Previous diff
Revision as of 02:35, 22 January 2006 (edit) (undo)
84.129.241.214 (Talk)
(Anyone with bug - database account - please add this)
Next diff →
Line 21: Line 21:
=Another Solution= =Another Solution=
-DD-WRT has an inbuild proxy feature that allows rewriting of html content to filter .+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. As this is load intense you may want to disable this feature.
This should be done under This should be done under

Revision as of 02:35, 22 January 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 or something else.
But using the Values below is not fixing the problem for everyone.

Solution

  • Go to the Web-Admin and log in
  • Go to 'Administration'
  • Go to 'Management'
  • Enter the folowing values at 'IP Filter Settings'
    • Maximum Ports: 4096
    • TCP Timeout (s): 90 or 120
    • UDP Timeout (s): 90 or 120


Screenshot

alt IP Filter Settings at DD-WRT v23

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 1. Though all 4 checkboxes are unchecked the rewriting proxy is still running 2. It drops connections if under heavy load 3. 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 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