1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

HyperWRT 2.0b3 network slowdown

Discussion in 'HyperWRT Firmware' started by snowpeas, Jan 6, 2005.

  1. snowpeas

    snowpeas Network Guru Member

    HyperWRT 2.0b3 network slowdown

    Hi all I need some help w/ the newest firmware from HyperWRT.
    I've used older versions but have not noticed until the most current version 2.0b3. The problem that I have with it is that if I run p2p program, mainly Bit torrent, then my network would come to a complete halt.

    For bt client, I use azureus the newest version. I have the ports fowarded. And after running for about 5 min, I would not be able to use the internet. The webpages would load until it timesout or it would just give me an error. I am guessing it doesn't happen right away because it takes a while to be connected to other peers with p2p.

    I went to linksysinfo.org and found other people have the same problems that I am having. But no solution was provided. »www.linksysinfo.org/modules.php?name=F..

    Does any other of you experience this problem? Is there a solution to my problem? As of now, I've switched my router back to BEFSR41 which gives me no problems whatsoever. Any comments would be appreciated.
  2. Avenger20

    Avenger20 Network Guru Member

    There is indeed a problem using heavy P2P (like bittorrent) and HyperWRT (or linksys) firmware.

    HyperWRT 2.0b4 will have fixes that should fix this problem. You may expect 2.0b4 within the next few days :)
  3. howardp6

    howardp6 Network Guru Member

    It is simple, you are maxing out the TCP connections (sockets) in the Linux OS on the WRT54G. Since you are already running hyperwrt, Try increasing the connection tracking from the default of 1024 by logging in and running the following. BitTorrent/p2p uses a lot of connections.

    put the following in a startup script (or enter it from a command shell)

    echo "4096" > /proc/sys/net/ipv4/ip_conntrack_max

    Aonther thing to try (via command shell or startup script) is

    echo "1800 3600 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts

    This changes the TTL to 1 hour (vs 5 days by default if i'm not mistaken). TTL, often overlooked, is the key for P2P stable connections on hardware firewalls.

    NOTE: Make changes to the IP settings on the WRT54G AT YOUR OWN RISK. The defaults were most likely chosen to give the best overall performance with the available hardware
  4. Gheimposse

    Gheimposse Network Guru Member

    Hi Avenger20 ... may you tell us which are the news in the upcoming 2.0b4 firmware you´ll release within the next days?
  5. pharma

    pharma Network Guru Member

    Avenger20 already mentioned in another thread this is basically bug fixes.
  6. snowpeas

    snowpeas Network Guru Member

    Sounds great I'll be looking foward to your new release. Thanks for all your help and your work!
  7. Avenger20

    Avenger20 Network Guru Member

    You can use the workaround from howardp6 for now.
    Those are the values I'm going to use in 2.0b4 as default.
  8. Ouaibe

    Ouaibe Network Guru Member

Share This Page