From: "Radosław Łoboda" <p0wer@tl.krakow.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Kazaa 2 and Shaping
Date: Tue, 10 Dec 2002 10:21:56 +0000 [thread overview]
Message-ID: <marc-lartc-103951552914302@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103950880808861@msgid-missing>
On Tue, 10 Dec 2002, Snuffy2 wrote:
> I'm sucessfully running a shaper on the trafic over my
> DSL. It works great except ...... I can't seem to get
> it to limit Kazaa usage. I'm not trying to turn of
> the Kazaa ports, but just put them at a very low
> priority. I know everyone says that Kazaa uses port
> 1214 which is true, but Kazaa 2 seems to use a whole
> slew of other ones (could be random, not sure). Is
> there a list of all the ports Kazaa 2 uses or a
> different, better way to limit Kazaa and place it low
> priority? Is there anyway to scan the IP header and
> determine that it's going/coming from Kazaa and limit
> it that way? Any help is appreciated as the users
> using Kazaa are flooding the connection ..... again.
You may try shaping everything that has source OR destination port 1214,
in both directions. This improves chances on reducing traffic since the
port 1214 is often used on any other side of connection.
I also saw some patch for iptables to stop kazaa (and other, based on
matching regexp's on data transferred) but i can't find it now.
--
##########################################
# | p0wer | #
# __ | GG#1877248 | #
# (oo) | p0wer@bojko.eu.org | #
# / \/ \ Go away or I will replace you #
# `V__V' with a very small shell script. #
##########################################
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-10 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 8:25 [LARTC] Kazaa 2 and Shaping Snuffy2
2002-12-10 10:21 ` Radosław Łoboda [this message]
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=marc-lartc-103951552914302@msgid-missing \
--to=p0wer@tl.krakow.pl \
--cc=lartc@vger.kernel.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