There are many ways that Bittorrent traffic can be handled
Handling Bittorrent traffic is never easy, as it requires fighting against a constantly evolving protocol with failsafes and users working o nit at all times. While the Exinda can help, it is never foolproof due to the speed that Bittorrent can change. However, here are some best practices that can be applied to the Exinda with regards to Bittorrent:
- Do not fully block Bittorrent traffic. Throttle it down to 1kbps. Bittorrent can detect that a connection has no packets being received and can start changing ports and masquarading as protocols, as it knows that it is being filtered. When it starts hopping ports and changing its signature, the effectiveness of the Exinda at catching the traffic will fall. Furthermore, if it changes its pattern so that it is passing itself off as mission critical applications, then it will get more bandwidth than wanted, choking the network. Throttling it down to 1kbps ensures that the connection will stay alive, but those connecting through it will never receive any meaningful data. That way, Bittorrent will not detect it is being filtered, and the users will get frustrated long before the ycan get any file.
- Change the Bittorrent Sensitivity as needed. Under Configuration > System > Setup, "Monitoring" tab there is the option to change the Bittorrent sensitivity level. By default, it is set at Medium. This is an acceptable setting. However, if traffic is seen as Bittorrent, it might be a good idea to turn the setting up to 'High'. Note however, this can cause false positives. Legitimate applications that use P2P connections (such as .NET, P2P heartbeating mechanisms, etc) can be wrongly classified as Bittorrent due to the hightened sensitivity. If this happens, please contact Exinda TAC
- Keep a Bittorrent policy at the top of the optimizer tree. This will ensure that the Bittorrent traffic will hit that policy first