From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: Are there any alternatives to IFB for downlink shaping?
Date: Mon, 16 Mar 2015 21:58:16 +0000 [thread overview]
Message-ID: <550751F8.30500@gmail.com> (raw)
In-Reply-To: <1426521620621.27129@farncombe.com>
Nick Pelling wrote:
> I was hoping (of course) that IFB would be able to do this for me,
> but it doesn't seem to want to play nicely. Am I missing something?
> All suggestions and comments very much appreciated! :-)
I think IFB should do here, Andrew already mentioned IMQ, but for normal
setups the only real need for that would be if you need to shape traffic
destined for the router as well as forwarded and then only if you have
to nat onto a single public address. Your setup seems to be just
forwarding so that doesn't apply.
You should be able to use ifb to catch traffic leaving on the lan facing
egress devices. Having previously marked using iptables
depending on dst if or mark with tc.
To use filters to redirect from both br0 and wl1 to a single ifb you
will need to add eg, a prio qdisc to br0 and wl1 (just because you can't
add filters to a device without a "real" qdisc on it, the default
pfifo_fast will not do).
One other thing to remember is that shaping traffic coming in from wan
is not the same as shaping that going out - you are at the wrong end of
the bottleneck and have to back off/sacrifice some bandwidth or you will
never build up a queue to do anything with. How much to back off
somewhat depends on the speed of the link and how much you care about
latency and how hard you hit the line eg shaping a few tcps is easier
than a few hundred from torrents.
next prev parent reply other threads:[~2015-03-16 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 16:00 Are there any alternatives to IFB for downlink shaping? Nick Pelling
2015-03-16 16:26 ` Marco Gaiarin
2015-03-16 16:58 ` Mike Schmidt
2015-03-16 16:59 ` Andrew Beverley
2015-03-16 21:58 ` Andy Furniss [this message]
2015-03-17 9:47 ` Nick Pelling
2015-03-17 11:36 ` Nick Pelling
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=550751F8.30500@gmail.com \
--to=adf.lists@gmail.com \
--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.