From: Derek <derek@traffic-power.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize P2P
Date: Tue, 30 Sep 2003 22:08:30 +0000 [thread overview]
Message-ID: <marc-lartc-106495979130069@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106461737829463@msgid-missing>
Wow,
That is an awesome module. I definately may be able to use that in the
future, thanks :) ... I just wish they had an iptables extension for instant
messenger clients, and then I'd be all set :)
Thanks again,
Derek
On Tuesday 30 September 2003 02:45 pm, miller69@gmx.net wrote:
> Hi,
>
> > I found that in one of previous posts, yet it doesn't recognize
> > eDoneky/Overnet which I need.
>
> there is an iptables extension called IPP2P to filter P2P traffic. It
> recognizes eDonkey/Overnet and other P2P networks as well. For traffic
> shaping it has to be used together with CONMARK. Go to
> http://ilabws13.informatik.uni-leipzig.de/~mai97bwf/delay.html there you'll
> find a setup currently in use and at the bottom of this page is the
> download-link for IPP2P.
>
> Hope that helps!
> Mike
--
-----------------------
Derek Fedel
Network Administrator
Ext. 238
Traffic-Power.com
"Hence the saying: If you know the enemy
and know yourself, you need not fear the result of a
hundred battles. If you know yourself but not the enemy,
for every victory gained you will also suffer a defeat.
If you know neither the enemy nor yourself, you will
succumb in every battle." - Sun Tzu
_______________________________________________
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-30 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 23:01 [LARTC] How to recognize P2P Jacek Bilski
2003-09-26 23:16 ` Derek
2003-09-26 23:31 ` Jacek Bilski
2003-09-29 15:03 ` Derek
2003-09-30 14:59 ` Jason A. Pattie
2003-09-30 21:45 ` miller69
2003-09-30 21:52 ` Jacek Bilski
2003-09-30 22:08 ` Derek [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-106495979130069@msgid-missing \
--to=derek@traffic-power.com \
--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