I’m seeing torrent users suck up literally all the bandwidth available to my Balance 380, pretty much shutting out everyone else. Although I can dump the specific users into the ‘Guest’ group to throttle them (or block them altogether via firewall), identifying them requires tedious monitoring of the Active Sessions and Client lists. How about adding a feature to limit torrent traffic to either 1) a percentage of total bandwidth, or 2) lowest priority of all traffic types, or 3) blocking it altogether? I know that identifying torrent traffic is not straightforward, what with random ports, etc., but there are some pretty obvious characteristics:
Client maintains high, rather steady download rate over time.
Client’s download/upload rate are close to equal.
Client maintains a high number of persistent connections.
The bulk of the Client’s connections are to addresses scattered randomly all over the planet.
These are the criteria I use to identify torrent hogs, and so far, no one has screamed ‘FOUL!’ due to my blocking their legitimate non-torrent activity. It would be a real time (and bandwidth) saver if the Balance could do the monitoring/throttling for us.