Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipp2p problem with kernel 2.6.20!
Date: Tue, 10 Apr 2007 22:24:13 +0000	[thread overview]
Message-ID: <461C0E8D.60008@andyfurniss.entadsl.com> (raw)
In-Reply-To: <1175784729.22316.3.camel@dunder>

Niclas Bentley wrote:
> Hi again,
> I wrote this a few days ago....Isn't there anybody using ipp2p and linux
> kernel 2.6.20?
> I think ipp2p would be very useful in order to identify bittorrent
> traffic...

I don't - maybe you should cc the maintainer aswell.

As for bittorrent - there may be easier (and fairer) ways, like per user 
  shaping or if you are doing QOS for yourself use a client that can 
bind to a different IP.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-04-10 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 14:52 [LARTC] ipp2p problem with kernel 2.6.20! Niclas Bentley
2007-04-10 22:24 ` Andy Furniss [this message]
2007-04-18  5:53 ` Andras Sarkozy

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=461C0E8D.60008@andyfurniss.entadsl.com \
    --to=lists@andyfurniss.entadsl.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