From: "rio@martin.mu" <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] KaZZaa and connection sequences
Date: Wed, 14 May 2003 06:43:27 +0000 [thread overview]
Message-ID: <marc-lartc-105289480806054@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105283048908146@msgid-missing>
Original Message:
-----------------
From: GoMi gomiuk@hotmail.com
>Hi there, i am having big touble wiht traffic shaping and kazza, by any
>>reason, it seems to collapse all the system. I have a firewall to stop
users >using p2p programs during day time, and then its totally free for
them to >>access anywhere during night-time.
>First problem Problem... KaZZa
>During day-time, there are kazza servers accepting connections on pot 80,
>>and because i cant filter that port, my users can dowload. I have tried
to >study the sequence of kazza programs using tcpdump, but i got no
conclusions, Does anybody know how to distinguish between HTTP connections
>>and KaZZa?
Kazaa is hard to stopped, did u already know that when you sniff your
clients connection using Kazaa, there are random tcp port range from 1214
until 4000 connecting from your clients to random and numerous ips outside.
So perhaps you need to shape all protocols going to your clients. That
worked for me. If you want in daylight is just for web browsing you could
use Squid as Bandwidth Limiter with its Delay Pool, and IPTABLES to block
all outgoing connection except port 80.
Regards,
Rio Martin.
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-14 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 12:53 [LARTC] KaZZaa and connection sequences GoMi
2003-05-13 13:24 ` Greg Scott
2003-05-13 13:24 ` Gordan Bobic
2003-05-13 13:48 ` Ethan Sommer
2003-05-14 6:43 ` rio [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-105289480806054@msgid-missing \
--to=rio@martin.mu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.