Applying QoS for encrypted BT traffic.

Discussion in 'HyperWRT Firmware' started by dolly_oops, Jul 27, 2006.

  1. dolly_oops

    dolly_oops Network Guru Member

    I'm sorry to bring this subject up again, but I'm just after a definitive answer.

    Due to my ISP strangling BitTorrent traffic, I have to encrypt it. I did have QoS working with BT before encryption, and I'd like to get it working with encryption.

    To get it working, I could do one of the following things:

    1) Getting the L7 filter to match against encrypted BitTorrent traffic. I'm guessing that my BT client won't be generating encrypted traffic in a consistent form, so even if I could define my own protocol matching filter, it wouldn't work.

    2) Bind all my outgoing connections on my machine to a single port, and then applying QoS to that port. But am I correct in thinking that the port ranges you define in HyperWRT only apply to OUTGOING DESTINATION ports, rather than OUTGOING SOURCE ports (which is what I want...)

    3) Mark BT packets with TOS flags - only thing here is that I'm unsure what settings I should be using (and I don't know whether the QoS in HyperWRT will do anything with it or not).

    4) Define QoS on the machine which does all the BT downloads. Not a bad idea, but I don't want to affect all traffic from that machine, so I'm guessing I would then have to explicitly define all other types of traffic to use a higher QoS setting before defining it. I'm hoping that the QoS rules I define are in order, so that HTTP traffic coming from my BT machine will match the HTTP rule first (high priority), without matching the MAC address rule (low priority). Is that the case?

    5) Put another network card in my BT machine, and route only BT traffic through it (all non-BT traffic from that machine then goes through the other network card). Not sure if that's doable or not in Windows 2000, but if I can, then at least I can apply QoS settings by MAC addresses.

    Can anyone tell me which of these ideas is likely to work?

  2. Thibor

    Thibor Super Moderator Staff Member Member

  3. dolly_oops

    dolly_oops Network Guru Member

  4. Thibor

    Thibor Super Moderator Staff Member Member

    if you set port qos to your bittorrent port, it will help. it will not catch ALL bittorrent traffic, as it uses so many ports. perhaps you can set ports 10000-65536 to low. that will exlude most of the legit ports, ie http/s, dns, etc. just select it in add application and define your chosen port ranges there. there will be the odd client that uses a low port, but it should be isolated.
  5. dolly_oops

    dolly_oops Network Guru Member

    OK, thanks for the suggestion. I was hoping I could setup something a bit more precise, but that will do.

    Just out of curiosity - if a packet matches one or more QoS rules, is it only affected by the first one it matches, or by all of them?
  6. Thibor

    Thibor Super Moderator Staff Member Member

    dunno, try it and let me know the result
  7. dolly_oops

    dolly_oops Network Guru Member

    Seems like all the rules take affect, regardless of what order they are applied.

    I had a setup where HTTP traffic was high priority, with BT running full speed (with data encryption on). HTTP was fairly responsive (though not as fast as it would be if the BT traffic was low priority).

    Added a setting where my MAC address was assigned low priority. HTTP was quite unresponsive. Adjusted rules so that the MAC rule came before the HTTP rule - no difference.

    I think the only options left are either to add the large port range setting as you suggested, or install another NIC in my machine (not entirely sure if that'll work anyway)...

    Thanks for the help.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice