netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: Lloyd Standish <lloyd@crnatural.net>
Cc: netfilter@vger.kernel.org
Subject: Re: htb + prio trouble (additional info)
Date: Sun, 20 Nov 2011 19:43:15 +0000	[thread overview]
Message-ID: <1321818195.2382.1003.camel@andybev-desktop> (raw)
In-Reply-To: <op.v49d61oxx1lyi3@debiandesk2.net>

On Sun, 2011-11-20 at 13:10 -0600, Lloyd Standish wrote:
> On Sun, 20 Nov 2011 12:44:46 -0600, Lloyd Standish <lloyd@crnatural.net> wrote:
> 
> > Hello All,
> >
> > While configuring a load-balancing router, I have run into trouble setting up traffic shaping (at least the load-balancing is working!)
> >
> > I am trying to:
> > (1) limit total upload speed to somewhat below the interface bandwidth
> > (2) do some traffic shaping, particularly avoid queuing of VOIP packets.
> >
> > To accomplish this I am trying to create a HTB qdisc on each outward-facing interface, each containing a PRIO qdisc with the default 3 classes.  sfq qdiscs are created for each PRIO class.
> 
> PS I should point out that in this case VOIP and DNS traffic should
>  always have priority, even at the expense of some bandwidth and/or
>  hurting other flows.

In which case the prio qdisc is the right choice.

>  I will look for better ways to filter for VOIP traffic

You might want to look at one of the traffic classifier projects such as
opendpi or l7-filter. You could maybe set a mark value and match that
using a tc filter with the "handle" parameter.

Andy



  reply	other threads:[~2011-11-20 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 18:44 htb + prio trouble Lloyd Standish
2011-11-20 19:10 ` htb + prio trouble (additional info) Lloyd Standish
2011-11-20 19:43   ` Andrew Beverley [this message]
2011-11-20 19:36 ` htb + prio trouble Andrew Beverley
2011-11-20 20:46   ` Lloyd Standish
2011-11-21 10:16     ` Andy Furniss

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=1321818195.2382.1003.camel@andybev-desktop \
    --to=andy@andybev.com \
    --cc=lloyd@crnatural.net \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).