All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Renzmann <mrenzmann@otaku42.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] small netwok traffic shaping
Date: Wed, 28 Jan 2004 14:55:36 +0000	[thread overview]
Message-ID: <4017CD68.6080508@otaku42.de> (raw)
In-Reply-To: <4017C135.8040703@nobugconsulting.ro>

Buna ziua, Adrian :)

Adrian Coman wrote:
> - if the users are using file sharing software, their bandwidth for such 
> applications must be limited to maximum 10kbps if noone else is 
> requesting bandwidth for normal http transfers, else the bandwidth must 
> be 0 for such applications.

There are two things that might be interesting for your work:

1. http://l7-filter.sf.net
That's a facility for either the QoS framework or iptables that enables 
to distinct between several application layer (iso layer 7, hence the 
name) protocols such as http and ftp. You could use that to apply 
special marks to packets which then help you to classify the packets.

2. http://rnvs.informatik.uni-leipzig.de/ipp2p/index_en.html
That's an extenstion to iptables which allows to mark connections that 
belong to common peer-to-peer applications (which would be helpful to 
apply the above quoted rule).

Unfortunately I can't give you any more pointers, as I'm myself new to 
the whole QoS-stuff. But I hope this will help you a little.

La revedere.
Mike

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-01-28 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 14:03 [LARTC] small netwok traffic shaping Adrian Coman
2004-01-28 14:55 ` Michael Renzmann [this message]
2004-01-29  6:44 ` Artūras Šlajus
2004-01-29  7:42 ` Michael Renzmann

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=4017CD68.6080508@otaku42.de \
    --to=mrenzmann@otaku42.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.