February 15th, 2005, 02:48 AM
Looking to Block P2P Traffic?
Let's face it. P2P networking takes up a considerable amount of bandwidth. Whether you are a network administrator for a college LAN (Local Area Network) or an ISP, some estimates place P2P consumption (especially BitTorrent) at 60%. However, figuring out the most practical solution for various administrators varies. Should you outright ban P2P traffic? Incorporate bandwidth throttles? NetEqualizer lets you choose from these options and much more.
ISPs are in a more precarious situation than say a college LAN administrator. If P2P traffic begins to saturate a college network, the LAN administrator does not have to worry all that much if the decision is made to filter or block file-sharing traffic. Perhaps some people may complain, but the loss of revenue is not a concern.
ISPs on the other hand must take this into heavy consideration. P2P traffic consumes an enormous amount of bandwidth compared to the amount of individuals that use it. For example, CacheLogic, a P2P measuring and network solutions firm, P2P traffic can consume a majority of the ISPs bandwidth, easily blowing away HTTP. Comparatively, only a relative few individuals actually utilize such high consumption protocols.
So here is the tricky part. ISPs know that P2P has helped fuel the broadband revolution. While not everyone uses BitTorrent; eDonkey2000, FastTrack, Gnutella, etc. are very popular. Block P2P users, an the ISP might face a significant backlash. Throttle their bandwidth, and the ISP might have similar results.
RTR (read the rest)