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] QoS by customer or by service ?
Date: Wed, 26 May 2004 19:03:20 +0000	[thread overview]
Message-ID: <200405262103.20827.stef.coene@docum.org> (raw)
In-Reply-To: <NHBBLNDNFKDMKNNKGOMMGEHGGLAA.gregoriandres@yahoo.com.ar>

On Tuesday 25 May 2004 20:56, ThE LinuX_KiD wrote:
> I have a policy doubt.
>
> Suppose next scenario:
>
> I've a Internet link (1 Mb upload, and 1 Mb download).
> That link is maneged with a Linux QoS box (HTB/eSFQ and so on).
>
> Suppose that I've 50 customers sharing Internet Link, and
> I must to assign 3 ranges of bandwidth for them.
>
> Gold customers: 128 kbits
> Silver customers: 64 kbits
> brass customers: 32 kbits
>
> Next, I create classes and filters in order to make
> rules to share internet link, with that limitations.
>
> But, what happen if someday I want to priorize VoIP traffic ?
>
> 1)I must to priorize VoIP traffic inside each customer class ?
> 2) or I must first all VoIP traffic, and next each customer class ?
>
> I think that 1)  is correct way, because I must to respect bandwidth
> for each customer, but I haven't experience with VoIP shaping
If you really have to respect the bandwidth / customer, then you have to do 
1).

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-05-26 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 18:56 [LARTC] QoS by customer or by service ? ThE LinuX_KiD
2004-05-26 19:03 ` Stef Coene [this message]

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=200405262103.20827.stef.coene@docum.org \
    --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.