On 09/08/03 09:58 +0530, Ripunjay Bararia (ILUG-MUM) wrote:
hi, What I read was that using patch-o-matic +netfilter(IPTables) and installing the string patch for iptables
Replies only to the list please.
you could at least begin to identify the packets from the clients running kazaa v2+, once identified you can do anything else you want with the packets, the main problem that I face is that the minute the packets are fragmented everything goes for a toss.
Welcome to freenet (pun intended).
some of the software out in the open :
http://p2pwall.sourceforge.net etc can be utilized to block ALL traffic to a client using Kazaa but this kind of policy can work in an corporate environment but I was more looking at implementing this in a ISP setup. where we do not have control over who uses what software.
Either throttle that connection, or choose not to service the user for excess traffic, or charge more for excess traffic. You really don't have another choice, unless you want to pay a lot of money. I know of a few solutions, but none of them are cheap.
http://www.snortsam.net with http://www.snort.org is something I have not yet tried doing still. But is there another easier way of doing this in an ISP environment.
I wouldn't touch that issue in an ISP environment with a 100 metre Cat5e cable. I am looking to change ISPs because they have this cisco PIX in front of the network with smtp fixup enabled and thye haven't turned it off for two weeks after telling them about it. Any ISP that interferes unduly in my network traffic without an explicit policy is about to lose a customer. Put a policy in place, and inform me about it so that I can choose to stay subscribed, or not. Oh, and don't top post.
Devdas Bhagat