All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Structuring my shaping
Date: Fri, 18 Oct 2002 06:38:02 +0000	[thread overview]
Message-ID: <marc-lartc-103492316806764@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103489653022215@msgid-missing>

On Friday 18 October 2002 01:14, Hayden Myers wrote:
> The shaping for my project needs to limit individual users while giving
> each user equal priority.  My thoughts are to create a root prio qdisc and
> then place a qdisc underneath that for each user.  Inside each of those
> qdiscs will be the classes to subdivide traffic based on port.  Is this
> the best way to accomplish what I want?
You can use the efsq (enhanced SFQ).  This qdisc is based on the sfq qdisc, 
but you can create the hash keys based on ip addresses and/or ports (both src 
and dst).  Attach that qdisc as the root qdisc and you are done.

If you want more control, you have to add a cbq or htb qdisc as the root qdisc 
and  create a class and filter for each user.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2002-10-18  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 23:14 [LARTC] Structuring my shaping Hayden Myers
2002-10-18  6:38 ` Stef Coene [this message]
2002-10-19 19:59 ` [LARTC] Structuring my shaping (fwd) Hayden Myers
2002-10-19 23:41 ` Stef Coene
2002-10-20  2:37 ` Folke Aeon
2002-10-20  4:20 ` Werner Almesberger
2002-10-21  3:45 ` Alexey Talikov

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-103492316806764@msgid-missing \
    --to=stef.coene@docum.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.