All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Boreham <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Too stupid to figure out shaping
Date: Wed, 27 Apr 2005 15:37:29 +0000	[thread overview]
Message-ID: <426FB1B9.8060209@boreham.org> (raw)
In-Reply-To: <200504271035.29546.jgorkos@wildcatwireless.net>

I also run a small wireless ISP, and we use HTB for shaping.
You need a separate class for each customer.
Alternatively I think it might be ok to use SFQ with
multiple customers in the same class, but for us the
class per customer works fine.

Fundamentally you need some mechanism that ensures
that each customer's packets are queued in their own queue.
Otherwise they will interfere with each other's QoS.


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

  reply	other threads:[~2005-04-27 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 15:35 [LARTC] Too stupid to figure out shaping John Gorkos
2005-04-27 15:37 ` David Boreham [this message]
2005-04-27 16:14 ` Brian Carrig
2005-04-27 18:42 ` Andreas Klauer
2005-04-27 22:19 ` John Gorkos
2005-04-27 23:04 ` Andreas Klauer

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=426FB1B9.8060209@boreham.org \
    --to=david_list@boreham.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.