We recently started relying on the 5508 AVC capability to block Bittorrent, which it seems to do fairly well. But... we are getting an increasing number of take-down notices where Bittorrent was used to do something, but drilling into the data in PI shows that nothing was detected by the WLC for the activity that led to the take-down. In other words, the system doesn't see the Bittorrent activity.
We have all three Bittorrent protocols in use (Bittorrent/encrypted/network), and can tell that most Bittorrent is indeed being blocked. But what is getting by is probably sufficient enough that we may have to abandon the WLC P2P strategy and go back to an appliance. Has anyone been through this, and found anything else to add to the profile to help stem the Bittorrent? (We also have the obvious ones like eDonky, etc) Thanks- Lee Lee Badman Wireless/Network Architect ITS, Syracuse University 315.443.3003 (Blog: http://wirednot.wordpress.com) ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
