From: miller69@gmx.net
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Kazaa
Date: Tue, 02 Sep 2003 09:29:49 +0000 [thread overview]
Message-ID: <marc-lartc-106249530026565@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106240635718517@msgid-missing>
Hi,
> I want to block (or limit) the Kazaa from our network. How can I do that?
> What tools should I use?
There is a tool called ipp2p to identify P2P traffic. It introduces a new
match module to iptables and allows you to catch the following P2P Networks
at
the moment:
-Fast Track (KaZaA and clones)
-Gnutella
-Edonkey (Edonkey, Emule, Overnet ...)
-Direct Connect
You can download it from:
http://ilabws13.informatik.uni-leipzig.de/~mai97bwf/ipp2p.tar.gz
To drop Kazaa data packets you just have to use the following
iptables-command:
iptables -A FORWARD -tcp -m ipp2p --kazaa -j DROP
This tool works pretty well as we tested it in a university environment.
Have a look and feel free to come back with any comments or suggestions to
me or
the author.
Regards,
Mike
--
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-02 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 8:49 [LARTC] Kazaa Awie
2003-09-01 10:01 ` Tom Verbeek
2003-09-01 15:34 ` gypsy
2003-09-02 0:43 ` Rio Martin
2003-09-02 7:53 ` Awie
2003-09-02 8:07 ` Robert Penz
2003-09-02 9:28 ` miller69
2003-09-02 9:29 ` miller69 [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-106249530026565@msgid-missing \
--to=miller69@gmx.net \
--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.