I'm having difficulties getting QoS rules to limit torrents to the point that I can run low pinging games on my network.
I have two interfaces:
- Internal: eth0 (LAN)
- External: eth1 (WAN/PPPoE)
Total available uplink bandwidth: 364 kbits/sec
Total available downlink bandwidth: 2114 kbits/sec
I have two definitions for torrents:
- uTorrent out: TCP/UDP 1:65535 → 24332
- uTorrents in: TCP/UDP 24332 → 1:65535
I have 2 Traffic Selectors for bittorent:
- P2P - Bittorent Out
DRECOMP2 (machine running torrents) → uTorrent out → Any
- P2P - Bittorent In
Any → uTorrent in → DRECOMP2 (machine running torrents)
On my Internal Interface in QoS I have 1 rule for bittorent:
- 2 P2P - Bittorent Down Limit
Guaranteed Bandwidth: 20 kbits/s
Specify upper bandwidth limit. Limit (kbit/s): 70
Traffic Selectors: P2P - Bittorent In
On my External Interface in QOS I have 1 rule for bittorent:
- 2 P2P - Bittorent Up Limit
Guaranteed Bandwidth: 5 kbits/s
Specify upper bandwidth limit. Limit (kbit/s): 20
Traffic Selectors: P2P - Bittorent Out
Please refer to the attached pictures if this isn't clear.
With these rules applies, uTorrent (which is specified to port 24332) runs completely uncapped, taking all bandwidth. The guarantees and limits I set are quite low compared to the speed internet I have (3mbit/512kbit). As you can see the priority number on the Interface QoS rules are "2". This is because I have similar rules set to priority "1" for Steam (client which runs games like Counter-Strike, service set to port range 27000:27050).
Am I completely missing something here? Are these rules not applied correctly? Does this QoS system not prioritize traffic according to the priority number next to each rule? I'm on firmware 7.104.
Any help is appreciated! Thanks guys!
This thread was automatically locked due to age.
