Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Bob Dhios on November 23, 2002, 12:47:34 AM
-
Hi, All
Anyone can help me? I need to blocking the kazaa port or sameone else port. Reading the forum files I found a lot of diferents way to do this. But I can't saw the best way to do this especific blocking.
Thanx
Bob
-
It's going to be kinda hard to do. In the newest versions of Kazaa you can specify which port to use. It will even go through port 80... kinda hard to block that one.
-
does Kazaa not need to connect to a particular remote host - ie their servers. could it not be blocked by adding a rule to the firewall to prevent any traffic out to that address / those addresses?
-
I havent blocked kazaa, but some other services with sqidguard.
You can find Kazaa-server lists everywhere 8-)) e.g. with google.
Then you have to put their adresses (name-adress or ip-adress) into the squidguard-database file.
They these will be blocked. - But there might be every day some others. Look at the suidguard-pages for further details.
with regards
Karl W. Müller
-
Kazaa doesn't use dedicated servers like the Napster P2P model.
If you're going to add all the server IP addresses, you'll be doing it constantly.
-
Andy MacDonald wrote:
>
> Kazaa doesn't use dedicated servers like the Napster P2P
> model.
> If you're going to add all the server IP addresses, you'll be
> doing it constantly.
Kazaa version 2 is almost impossible to block. At one stage I had about 30 acls attempting to blocking it, and it was still getting through. Version 1 was easy, sport 1414 I think it was, but version 2 has an almost endless supply of hosts and ports to try.
What you need is a corporate policy on using p2p applications, some simple rules such as matching the connection to the kazaa media desktop will inform you who is using this software, then warn them, and if pain persists, terminate their employment.
--
Damien
-
Good Morning,
I have been reading this information with interest. The only answer I can see is an add-on that blocks everything but the obvious ports. Then again, this is defeated if Kazaa goes through port 80 eventually. Bess is used at the school where I work and they are successful at blocking it. I don't know exactly how but they do. Is there anyway of blocking the protocol instead of all the ports? Is the P2P protocol recognizable(?) by sniffers and/or squidguard?
Just curious.
Later
Wally