Does anyone have any ideas to track down illegal bittorrent users that are encrypting it? We want to do anything we can to keep illegal usage off the network and in the process free up bandwidth on the tower.
Put a NTOP box in at your headpoint. you can track bandwidth hour by hour so you can see who is streaming for long periods of time.
Well we’ve been looking at a program by Colasoft called Capsa. If their running bittorrent encrypted though how do we know if they’re transferring illegal material? We can’t just assume that because they’re using bittorrent that it’s illegal (even though we all know it probably is 
Do you have already isolate APs (in the cmm) and SMs(in the AP)?
This reduces the broadcast over the wireless platform.
We’re using a Last Mile Gear CTM and a cisco switch there instead of a CMM micro.
What kind of Cisco switch? If you are not using VLANs I strongly suggest making use of the “port protected” feature to segregate traffic between APs and kill broadcast storms. Does your switch support SPAN or RSPAN so you can look at each AP? You could then plunk something in with Wireshark and determine the culprit.
We’re using a 2955. I’m not sure if we have those features enabled or not.
You could deploy a DPI solution from a company such as Allot Communications. You would then have the ability to throttle traffic based on service types such as P2P.
However this then brings up the controversy on “Net Neutrality” as you will be advocating restrictions based on content.
http://en.wikipedia.org/wiki/Network_neutrality
http://en.wikipedia.org/wiki/Network_neutrality_in_the_United_States
http://en.wikipedia.org/wiki/Network_neutrality_in_Canada
mbsi wrote: However this then brings up the controversy on "Net Neutrality" as you will be advocating restrictions based on content.
Quite right - one of my favorite methods is limiting the number of flows a subscriber can have open. This has the effect of stomping the most destructive P2P, unfortunately as well as some games. However it is completely protocol agnostic. It also can help if a customer suddenly contracts a virus by limiting the amount of damage that can be done.
This worked quite well for us as any customers running a lot of BitTorrent or any of the gnutella-based/like P2P programs would often call up complaining that their connection didn't work. We then took the time to explain how P2P programs were bad for wireless and helped them reconfigure their app so it didn't cause damage (cap # of connections and bit rate). Let the rate policers in the SMs take care of the rest.
pcpolo wrote: We're using a 2955. I'm not sure if we have those features enabled or not.
These should help:
http://www.cisco.com/en/US/docs/switche ... #wp1158863
http://www.cisco.com/en/US/docs/switche ... wspan.html
helped them reconfigure their app so it didn't cause damage (cap # of connections and bit rate). Let the rate policers in the SMs take care of the rest.
Heya Salad, can you point me in the direction of configuring these P2P either something online or something?
Thanks
Well, here’s how to make it go faster for a popular program, so I’d say just turn some of those numbers around and you’re set http://www.johntp.com/2006/04/19/how-to … -utorrent/
In most apps it will be something like Tools -> Options -> Connections or Transfers or something like that.