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

Unable to connect to WiFi during Bittorrent download

Discussion in 'Tomato Firmware' started by AlpineMan, Apr 23, 2007.

  1. AlpineMan

    AlpineMan Network Guru Member

    I have a Buffalo WHR-G54S w/ the latest Tomato firmware (router1). I have another WHR-G54S w/ Tomato (router2) connected to router1 via WDS and a Linksys WRT54GL w/ DD-WRT SP2 (router3) also connected to router1 via WDS. I have two PC's connected to router1's wired LAN ports. I performed a test Bittorrent download (2.5gb in size) on one of the PC's...everything was going fine...download speeds were at 450kB/s...but the only thing is...I could not get any other PC's to connect to any of my WDS AP's. In fact, I could not even ping any of the other routers from the wired PC's...and when I could ping, it was like 3000ms response time or so...but most of the time, I get time outs. I tried playing around with my Bittorrent client's (Azureus) settings, but it didn't help. As soon as the download finished, PC's connecting to any of the WDS's could connect fine...and I could ping both router 2 and 3 from my PC connected via wired in router 1.

    Are there any particular settings in Tomato where I need to make adjustments so that downloads like these don't prevent WiFi connectivity to any of my routers?
  2. dolly_oops

    dolly_oops Network Guru Member

    At a guess - you could reduce the number of global connections you have in Azureus, see if that makes a difference. Alternatively, you could increase the number of connections allowed by Tomato.

    That's the only thing I can think of at the moment, sorry.
  3. Toxic

    Toxic Administrator Staff Member

    Also set your priority of BT to a low setting and set DHCP service to highest.
  4. AlpineMan

    AlpineMan Network Guru Member

    I put 4096 as max connections in router1 and I put 30 in Azureus during the file xfer. It didn't fix the problem. I'll try playing w/ the QoS.

    BTW, I'll be getting my Sunrocket Gizmo today...any suggested QoS sEttings? This will be attached to router2.

  5. AlpineMan

    AlpineMan Network Guru Member

    I got my problem resolved...also got my SunRocket Gizmo working even during download/upload of Bittorrent. See attached Tomato QoS settings.

    Attached Files:

  6. dolly_oops

    dolly_oops Network Guru Member

    The ports in your QoS settings - are they the source ports?
  7. AlpineMan

    AlpineMan Network Guru Member

    I just put SRC and DST ports...but if I'm to guess, they would be SRC ports. I also did some more tweaking in my settings, I changed the default class to Low instead of Lowest.

    (update)...my bad...after changing default class to Low, I noticed some BitTorrent stuff were being qualified as low...so I changed default class back to Lowest.
  8. dolly_oops

    dolly_oops Network Guru Member

    I just wondered why you had the IPP2P filter as well as the SRC / DST port check on...

    If you are in control over all BitTorrent clients which are going to be run over your network, you might want to try and configure this:

    This is how I set up QoS to apply to my BitTorrent connections:
    1) Set up your BT client to bind all outgoing connections to a given port (both Azureus and µTorrent allow this).
    2) Set up your BT client to use a specific port for all incoming connections.
    3) Use Tomato's QoS to match both of these SOURCE ports (not destination ports) and categorise them as you want.
    4) Place this rule higher than any other QoS rules which rely on the destination port.

    You shouldn't rely on matching by protocol, since encrypted connections won't get picked up (I'm not saying you shouldn't use it, I'm just saying that it's not foolproof). If you're able to use my suggestion above, then you won't need to use protocol matching.

    Alternatively, you could do the following:
    - If your client doesn't set binding outgoing connections to a specific, you could just try matching by protocol. You may want to disable your client from making or receiving any encrypted connections - that should prevent any BitTorrent related connections from bypassing the filters.
    - You could make assumptions based on port numbers. If you have QoS rules which will be placed higher than any other BitTorrent QoS rules which are based on ports, you could set your BitTorrent client to refuse to connect to other peers which are using ports usually reserved for other types of traffic (80 for HTTP, 21 for FTP, 22 for SSH, 23 for Telnet, 443 for HTTPS etc). That will prevent those rare situations where you give a BT connection a much higher priority because of the port it is using.
    - You can use an approach based on destination port ranges. You could either make the assumption that any destination ports not covered by higher placed QoS rules is BitTorrent (or P2P traffic) - but that means you would have to then explicitly define rules for all common types of traffic (this would work well with the above suggestion). Alternatively, you could assume any high numbered destination port (say 1024 - 65535) is BitTorrent traffic, except that any BitTorrent connections with a destination port lower than this will not be categorised correctly - there's also still the (smaller) chance that you might be incorrectly categorising connections as BitTorrent.
  9. AlpineMan

    AlpineMan Network Guru Member

    I followed an example posted by someone here on their QoS settings...it seemed to work, so I let it alone.

    Choosing the SRC port only...does it work for you? Is it more efficient doing SRC port only?
  10. dolly_oops

    dolly_oops Network Guru Member

    Yes it works for me (the very first rule I have for QoS is for BitTorrent based on source port). It would be quicker for the router to categorise BitTorrent traffic that way rather than by protocol.

    As I said, if you've got a decent enough BitTorrent client which supports binding to a port in that way, and you've got control over every machine which is going to be using BitTorrent, then categorising that way would be best in my opinion. If you can't do that, then you can always try one of the other suggestions I made.
  11. AlpineMan

    AlpineMan Network Guru Member

    dolly_oops, would you mind posting screenshots of your QoS? Thanks.

Share This Page