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

Which Thibor Firmware - Will it solve bitorrent issues?

Discussion in 'HyperWRT Firmware' started by tododo, Jan 3, 2006.

  1. tododo

    tododo Network Guru Member

    Hi people

    Sorry to ask a question which has probably been asked before on the site. I have had a search around and there is a lot of info but I cant seem to find the answer

    Bascially I have recently purchased a WTR54GS version 1.1

    I have installed the latest stable version of HyperWRT (version 2)

    However I have been reading that there is a problem with this router and bitorrent, something about keeping bittorrent connections alive.

    Now I see there are alternate versions of HyperWRT that solve this issue - hopefully

    Does the latest release of Thibor solve this bitorrent problem or will I have to use a script aswell

    Thanks for any advice guys
     
  2. Thibor

    Thibor Super Moderator Staff Member Member

    basically i added gui options to change tcp_timeout and conntrack_max settings which help for bittorrent. i set tcp_timeout(ESTABLISHED but idle) to 600 seconds by default(from 432000) and conntrack_max still has a default of 2048, but can be changed. these controls are in Management.asp
     
  3. tododo

    tododo Network Guru Member

    Thanks Thibor

    Will get the latest version on asap and see how it goes
     
  4. Toxic

    Toxic Administrator Staff Member

    you also need to tweak bittorrent. lower the amount of connections it uses first of all. bittorrent is one of the only programs that grabs bandwidth and doesn't release it for anything else.
     
  5. purephase

    purephase Network Guru Member

    The only solution I ever found was to use the schedule component of your BT application (uTorrent and Azureus both have them) and during the hours where browsing/VOIP etc. are important (before/after work, during weekends) turn off BT.

    I've never been able to get this to work successfully with VOIP (regardless of QoS settings -- I believe the max connections limit has nothing to do with throttling specific ports and priority, it still using those connections).
     

Share This Page