datamike
July 23rd, 2003, 18:28
Hi, What is the best way to block people from using Kazza lite? I tried
blocking out port 1214 tcp and udp but it didn't work. I also tried blocking port 1214 on incoming and it didn't work. Thanks.

datamike
August 5th, 2003, 10:32
I came up with my own solution after googleing for a week. Hope this helps someone else too. Any input is appreciated.

Blocking Kazaa is more difficult than it may seem. Kazaa's default setting is port 1214 but is able to cycle through ports 1000 to 4000. Even if all these ports are blocked it is still able to attach itself to port 80, web surfing, and drastically slow down your web traffic. You can’t block port 80 without disabling valid web traffic.

The best way to stop Kazaa is to use a combo firewall/proxy setup. The firewall will only allow outgoing ports of 21, 22, 23, 25, 443, 551, 5631, and 5632. All other traffic is disabled. Every PC’s browser will have the proxy’s IP address and port enabled. The proxy will have an unusual port number like 9230. Normal web traffic going through port 80 will not work because of the firewall so everyone will be forced to go through the proxy.

Each PC will still have their DNS and gateway settings for other programs such as Email clients and SSH/Telnet emulators.

elmore
August 5th, 2003, 11:00
mike good to see you,

We've blocked kazaa in the past by simply blocking their enitre public sunbet block.

|MiNi0n|
August 5th, 2003, 11:09
We've blocked kazaa in the past by simply blocking their enitre public sunbet block.

Wasn't that napster elmore? Should work in principle the same as kazaa I suppose... block the initial login and s'all good :)

datamike
August 5th, 2003, 11:12
Thanks Elmore, been on a Red Hat kick for a while with all this Oracle stuff, time to get back to Open BSD. Do you happen to know what the IP block is? Thanks.

elmore
August 5th, 2003, 11:18
hrmmm lemme see if I can dig it up:

this one possibly:

block out log quick on $ExtIF from any to 213.248.112.0/24

frisco
August 5th, 2003, 11:28
There was a related thread on misc@ recently: http://marc.theaimsgroup.com/?l=openbsd-misc&m=105957875204283&w=2

Nick Holland has some good suggestions - essentially, muck around with dns so the login servers don't resolve.

datamike
August 5th, 2003, 12:06
Elmore, blocking that IP block did not work. Was that the correct one or were you just guessing?

elmore
August 5th, 2003, 12:09
as minion said above that musta been napster not kazaa. Sorry.
A dig reveals that kazaa.com is located in this block:


;; ANSWER SECTION:
kazaa.com. 19m50s IN A 212.100.253.45
kazaa.com. 19m50s IN A 212.100.253.44

I'm not sure if all their servers are located here but it's a place to start.

Sorry about that mike!