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

How to optimize Tomato for P2P?

Discussion in 'Tomato Firmware' started by Frustian, Jan 30, 2008.

  1. Frustian

    Frustian LI Guru Member

    I recently switched from DD-WRT to Tomato on my WRT54GL, and my P2P speeds plummeted from 300kB/s down 75kB/s up to 20kB/s both ways. This has nothing to do with different files/times of the day/whatever else you may think about it, this is from the router.

    The weird thing is, the first 4 minutes when I was configuring the router everything was fine, and I was getting normal speeds, since then the speeds dropped. I can't think of anything I did to provoke that, I believe I was only entering in wireless security at that time, and the computer is has a wired connection.

    -The ports are forwarded
    -QoS is OFF, but I deleted the catch-all entry anyways.
    -There are only ~200 established connections, well below the 2k limit I have. I really don't know how to deal with that many specific timeouts though so I haven't touched them, I'm used to one for TCP and one for UDP.

    I have liked everything about Tomato so far but this, and I'm not going to give up on it yet, but I may switch back to dd-wrt if I can't fix it.
  2. pharma

    pharma Network Guru Member

    Try a forum search ... this has been discussed many times. As for me I did not have to change the default settings to attain P2P download speeds of up to 800 kB/s.

  3. szfong

    szfong Network Guru Member

    port forwarding via manually (preferred) or uPnP (if verified) and saturation of upload bandwidth are two reasons I can think of assuming everything on computer are same.
  4. Frustian

    Frustian LI Guru Member

    Thank you for the replies, it turns out I didn't enter the correct port to be forwarded (typo), uPnP is off.
  5. szfong

    szfong Network Guru Member

    you should use upnp, some isp will throttle you based on port usage. I randomize ports on my client each time it restarts and run a script which restarts the client every 18 hours or so based on what tomato shows at the point of slow speed.

Share This Page