From: Luciano Ruete <kies@myrealbox.com>
To: netfilter <netfilter@lists.netfilter.org>
Cc: arnt@c2i.net
Subject: Re: Yet Another Kazaa Issue
Date: Thu, 21 Nov 2002 22:36:25 -0300 [thread overview]
Message-ID: <3DDD8A19.8000704@myrealbox.com> (raw)
In-Reply-To: 001001c2900d$fa96b2f0$0200000a@parseerror.dk
Matias Bjørling escribió::
> 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
I did two thing (in diferent situations) that works very well.
1º hit the kazaa Achilles heel --> the centralized server
iptables -A FORWARD (...) -d 206.142.53.0/24 -j REJECT
iptables -A FORWARD (...) -d 213.248.112.0/24 -j REJECT
This work 4 me, i dont know if the nets are the same today, but 'try and
tell!' or google it =)
2º i have CBQ'ed both incoming and outcoming kazaa traffic, you can
drive the thins as far as you whant, and give 1kbit to all the kazaa
conections behind de router/firewall.
Here is my conf to cbq.init (the most simple case)
Two files, 1 for up, 1 for down
/etc/sysconfig/cbq/cbq-120.kazaa-up
DEVICE=eth0,10Mbit,1Mbit
RATE=120Kbit
WEIGHT=12Kbit
PRIO=5
RULE=:1214,
RULE=,:1214
/etc/sysconfig/cbq/cbq-240.kazaa-down
DEVICE=eth1,10Mbit,1Mbit
RATE=240Kbit
WEIGHT=24Kbit
PRIO=5
#RULE=:1214,
#RULE=,:1214
You can find cbq.init (a script/frontend to tc and CBQ classes) in
https://sourceforge.net/projects/cbqinit
The script is self documented
Regards
--
Luciano
next prev parent reply other threads:[~2002-11-22 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 20:55 Yet Another Kazaa Issue Matias Bjørling
2002-11-22 1:36 ` Luciano Ruete [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 20:55 Matias Bjørling
2002-11-21 22:15 ` Aldo S. Lagana
2002-11-22 11:19 ` Maciej Soltysiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DDD8A19.8000704@myrealbox.com \
--to=kies@myrealbox.com \
--cc=arnt@c2i.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox