From: "Aldo S. Lagana" Subject: RE: Yet Another Kazaa Issue Date: Thu, 21 Nov 2002 17:15:45 -0500 Sender: netfilter-admin@lists.netfilter.org Message-ID: <002401c291ab$897c8730$3864a8c0@discmail.com> References: <001101c2900e$055b0bf0$0200000a@parseerror.dk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C29181.A0A67F30" Return-path: In-Reply-To: <001101c2900e$055b0bf0$0200000a@parseerror.dk> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: =?iso-8859-1?Q?'Matias_Bj=F8rling'?= , netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C29181.A0A67F30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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. =20 =20 -----Original Message----- From: netfilter-admin@lists.netfilter.org [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Matias Bj=F8rling Sent: Tuesday, November 19, 2002 3:55 PM To: netfilter@lists.netfilter.org Subject: Yet Another Kazaa Issue Hey =20 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 =20 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 =20 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 =20 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 :( =20 Any help will be appreciated :D =20 Thanks =20 - SilverWolf ------=_NextPart_000_0025_01C29181.A0A67F30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
The=20 only real way to stop KaZaA, messenger, etc. is to use an = Application Proxy=20 and use the power of the proxy to stop traffic.  For example on = Linux you=20 could use the TIS toolkit, or Squid as proxies...you would redirect all = traffic=20 from iptables to them and then they would use their advanced methods of = looking=20 into the packets to allow or drop the packet.
 
 
-----Original Message-----
From:=20 netfilter-admin@lists.netfilter.org=20 [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of = Matias=20 Bj=F8rling
Sent: Tuesday, November 19, 2002 3:55 = PM
To:=20 netfilter@lists.netfilter.org
Subject: Yet Another Kazaa=20 Issue

Hey
 
Im trying like hell to get Kazaa to = stop connect=20 successfully... Whatever i do, blocking port 1214 in ANY possible way, = it=20 still resist and connect sucessfully, even with thoes firewall=20 rules
 
iptables -A FORWARD -m string = --string=20 "X-Kazaa-Username:" -j DROP
iptables -A FORWARD -m string --string=20 "X-Kazaa-Network:" -j DROP
iptables -A FORWARD -m string --string=20 "X-Kazaa-IP:" -j DROP
iptables -A FORWARD -m string --string=20 "X-Kazaa-SupernodeIP" -j DROP
iptables -A FORWARD -m string = --string=20 "Kazaa" -j DROP
 
Chain=20 FORWARD (policy DROP)
target     prot opt=20 = source           &= nbsp;  =20 destination
DROP       all  = -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match X-Kazaa-Username:
DROP       = all =20 -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match X-Kazaa-Network:
DROP       = all =20 -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match X-Kazaa-IP:
DROP       = all =20 -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match X-Kazaa-SupernodeIP
DROP      =20 all  -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match Kazaa
LOG        all  = -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match User  LOG level = warning
DROP      =20 all  -- =20 = anywhere           = ; =20 anywhere           = STRING=20 match User
state_chk  all  -- =20 = anywhere           = ; =20 anywhere
 
It catch the "kazaa" thingie on the = homepage...=20 But.. anyhow it somehow seem to connect to the supernode outside... Im = getting=20 nuts.. Why can't i stop it?.. What am i doing wrong.. I tried to ages = now..=20 and it dont work :(
 
Any help will be appreciated = :D
 
Thanks
 
-=20 SilverWolf
------=_NextPart_000_0025_01C29181.A0A67F30--