All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Bilski <dino@camelot.homedns.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize P2P
Date: Tue, 30 Sep 2003 21:52:38 +0000	[thread overview]
Message-ID: <marc-lartc-106495883328911@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106461737829463@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Ehlo!

On wto, 2003-09-30 at 23:45, 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.

It's something I'll probably like. Now I use CONNMARK extension and
IPP2P seems to be remedy for my problems. I don't want to drop P2P, but
to limit it to only take bandwidth that was left by other services.

Thanks, I'll look into in.

Greetings!

-- 
Jacek Bilski <dino@camelot.homedns.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-09-30 21:52 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 [this message]
2003-09-30 22:08 ` Derek

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-106495883328911@msgid-missing \
    --to=dino@camelot.homedns.org \
    --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.