Chris Green wrote: > > I'm looking for a standard set of rules/filters to enable for all of my > customers to help block all of these applications. Does anyone have a > methodology that has been effective to do this? Does anyone have a list of > IP addresses we can block access to that will help? Will a content > filtering subscription successfully block these, or only help prevent > download of the apps?
Here's a method I use successfully: http://www.holland-consulting.net/tech/imblock.html Not sure if GB's DNS server can do that..however, the strategy could be used to pick out a set of IP addresses that can be used to squash most "problem" services, though if you go by IP over DNS name, you will have to stay on top the list of IP addresses. There are some other strategies that can be used. I have heard (though not verified) that Kazaa has a prefered port. If you block that port, it will happily slip out another port...but if you RATE LIMIT that port to some absurdly low level (say, 10kbps), Kazaa will stick to that port, but be unable to move much data, and hopefully, the users will give up. This suggests an alternative solution: If one wishes to tackle this problem from an administrative rather than technical side, just log the default ports of these apps... When you get an alert that someone has sent data to the Kazaa default port, deal with the person (this is probably more effective in a slow economy than in a growing one, if you get my drift ;-). Not sure how many apps have this style of "default" port, vs. how many just use a random port, once I figured out my solution above, I haven't had reason to look closer... Nick. -- http://www.holland-consulting.net ------------------------------------------------------ To unsubscribe: [EMAIL PROTECTED] For additional commands: [EMAIL PROTECTED] Archive: http://archives.gnatbox.com/gb-users/
