From: Matthias Weingart <lartc@pentax.boerde.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Intelligent P2P detection
Date: Thu, 27 Mar 2003 20:15:10 +0000 [thread overview]
Message-ID: <marc-lartc-104879620209041@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104857984213566@msgid-missing>
Maybe another way is better. What is the most common of P2P traffic? It
makes much much traffic. So let us catch it there. Monitor the traffic of
one IP and if the traffic within a certain time is high, the bandwidth of
this IP is set down to a lower level automatically (or put in lower priority
queue). After some time - the transfer has finished - it is set back to the
normal level. (I am quite new to qos and HTB and I wonder if this can be done
with linux?). This way you limit all big transfers, nevertheless they are
done by ftp, http or P2P.
I guess it will be _very_ difficult to find and mark all packets of P2P
software (and you will always be behind if new software or new versions are
published).
M.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-03-27 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 8:08 [LARTC] Intelligent P2P detection Luman
2003-03-25 10:21 ` Kim Jensen
2003-03-25 10:53 ` Luman
2003-03-25 12:20 ` Kim Jensen
2003-03-25 12:24 ` Luman
2003-03-25 12:30 ` Luman
2003-03-25 12:44 ` Matthias Weingart
2003-03-25 12:51 ` Robert Kryczało
2003-03-25 12:56 ` Luman
2003-03-25 13:05 ` Robert Kryczało
2003-03-25 15:27 ` Robert Kryczało
2003-03-26 21:37 ` Dawid Kuroczko
2003-03-26 21:50 ` Dawid Kuroczko
2003-03-27 9:24 ` Luman
2003-03-27 9:35 ` Luman
2003-03-27 10:16 ` Gordan Bobic
2003-03-27 15:20 ` Robert Kryczalo
2003-03-27 15:32 ` Robert Kryczało
2003-03-27 16:04 ` Gordan Bobic
2003-03-27 16:38 ` Robert Kryczało
2003-03-27 16:43 ` Gordan Bobic
2003-03-27 20:15 ` Matthias Weingart [this message]
2003-03-27 21:34 ` Arvid Stüwe
2003-03-28 8:14 ` Robert Kryczało
2003-03-31 12:10 ` Szymon Miotk
2003-03-31 12:32 ` Patrick McHardy
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-104879620209041@msgid-missing \
--to=lartc@pentax.boerde.de \
--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.