Hi Even if kazaa uses ports that can be set by the user, there must surely be some kind of control connection when the client starts up that it uses to establish connection to the kazaa network and tell other clients about it's port number. Just try to figure out (ethereal, tcpdump) what the initial connection is. With gnutella there is an initial http connection to the 'servers'. Ray On Tue, 2003-03-25 at 17:57, Maciej Soltysiak wrote: > > I am unaware of any specific netfilter technique to simply block the > > newer versions of kazaa. Wish I could help you further. Good Luck. > I have heard of people using the string match to reject packets with > "X-Kazaa-User" or some other string. > > Also, you could try to block access to the network pool of dns.kazaa.com. > I think this way if the clients have not been ever using kazaa, will not > get addresses of other kazaa nodes. But it is a wild guess. > > Regards, > Maciej Soltysiak -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ( Raymond Leach ) ) Knowledge Factory ( ( ) ) Tel: +27 11 445 8100 ( ( Fax: +27 11 445 8101 ) ) ( ( http://www.knowledgefactory.co.za/ ) ) http://www.saptg.co.za/ ( ( http://www.mapnet.co.za/ ) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ o o o o .--. .--. | o_o| |o_o | | \_:| |:_/ | / / \\ // \ \ ( | |) (| | ) /`\_ _/'\ /'\_ _/`\ \___)=(___/ \___)=(___/
Attachment:
signature.asc
Description: This is a digitally signed message part
