By now you may or may not have noticed that a few bittorent clients have developed a work around for traffic shaping. Now these clients are encrypting packet headers and payloads to disguise their actual content, this means they can go unmetered/unfiltered on our networks.
These new bittorrent clients use unreserved, randomly generated ports for transmitting and recieving data. I started noticing large amounts of traffic on odd ports, TCP 1024, and other high port numbers. The only temporary solution I have for this is to block the port its connecting on for a limited amount of time till the client loses the connection, but you can't block these port indefinately as it could be used for legitimate purposes (http uses randomly generated src ports using the same ranges bittorrent is using).
What if anything can be done to combat this? I haven't had a chance to look into this further but does bittorrent have any centralized authentication server? I don't really want to block it, I just don't want the damn protocol consuming 1000kbps for hours on end. No where in my SLA does it say you have dedicated bandwidth 24/7. The only option I have is to scale the user back to a slower queue and when they complain explain the situation..