Yet Another Kazaa Issue
Hey
Im trying like hell to get Kazaa to stop connect successfully... Whatever i do, blocking port 1214 in ANY possible way, it still resist and connect sucessfully, even with thoes firewall rules
iptables -A FORWARD -m string --string "X-Kazaa-Username:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-Network:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-IP:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-SupernodeIP" -j DROP iptables -A FORWARD -m string --string "Kazaa" -j DROP
Chain FORWARD (policy DROP)
target prot opt source destination DROP all -- anywhere anywhere STRING match X-Kazaa-Username: DROP all -- anywhere anywhere STRING match X-Kazaa-Network: DROP all -- anywhere anywhere STRING match X-Kazaa-IP: DROP all -- anywhere anywhere STRING match X-Kazaa-SupernodeIP DROP all -- anywhere anywhere STRING match Kazaa LOG all -- anywhere anywhere STRING match User LOG level warning DROP all -- anywhere anywhere STRING match User state_chk all -- anywhere anywhere
It catch the "kazaa" thingie on the homepage... But.. anyhow it somehow seem to connect to the supernode outside... Im getting nuts.. Why can't i stop it?.. What am i doing wrong.. I tried to ages now.. and it dont work :(
Any help will be appreciated :D
Thanks
- SilverWolf
The only real way to stop KaZaA, messenger, etc. is to use an Application Proxy and use the power of the proxy to stop traffic. For example on Linux you could use the TIS toolkit, or Squid as proxies...you would redirect all traffic from iptables to them and then they would use their advanced methods of looking into the packets to allow or drop the packet.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Matias Bjørling
Sent: Tuesday, November 19, 2002 3:55 PM
To: [email protected]
Subject: Yet Another Kazaa Issue
Hey
Im trying like hell to get Kazaa to stop connect successfully... Whatever i do, blocking port 1214 in ANY possible way, it still resist and connect sucessfully, even with thoes firewall rules
iptables -A FORWARD -m string --string "X-Kazaa-Username:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-Network:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-IP:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-SupernodeIP" -j DROP iptables -A FORWARD -m string --string "Kazaa" -j DROP
Chain FORWARD (policy DROP)
target prot opt source destination DROP all -- anywhere anywhere STRING match
X-Kazaa-Username:
DROP all -- anywhere anywhere STRING match
X-Kazaa-Network:
DROP all -- anywhere anywhere STRING match
X-Kazaa-IP:
DROP all -- anywhere anywhere STRING match
X-Kazaa-SupernodeIP
DROP all -- anywhere anywhere STRING match
Kazaa
LOG all -- anywhere anywhere STRING match
User LOG level warning
DROP all -- anywhere anywhere STRING match
Userstate_chk all -- anywhere anywhere
It catch the "kazaa" thingie on the homepage... But.. anyhow it somehow seem to connect to the supernode outside... Im getting nuts.. Why can't i stop it?.. What am i doing wrong.. I tried to ages now.. and it dont work :(
Any help will be appreciated :D
Thanks
- SilverWolf
Quoted 5 lines
iptables -A FORWARD -m string --string "X-Kazaa-Username:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-Network:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-IP:" -j DROP iptables -A FORWARD -m string --string "X-Kazaa-SupernodeIP" -j DROP iptables -A FORWARD -m string --string "Kazaa" -j DROP
I recommend REJECT --reject-with tcp-reset.
It will tell the clients that the connections is closed. If you drop the packets, the clients will try to send packets on and on for some time.
Maciej Soltysiak