From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: PRIO qdisc traffic does not work as expected
Date: Sun, 06 Jul 2014 17:14:32 +0000 [thread overview]
Message-ID: <53B983F8.9030509@gmail.com> (raw)
In-Reply-To: <53A1697C.3040400@laposte.net>
GGounot wrote:
> I've made the following script.. It should redirect traffic according
> to TOS, but SSH, SCP, HTTP download, etc., but it does not and
> everything goes through 1:2.
Like David said - prio is not the best way to go as it may totally
block. I have never personally used it, prefering to do prio with htb -
still leaving the lowest class with a trickle.
If you are catching incoming traffic then it's possiblr that TOS won't
work as it could be cleared upstream. I have never relied on TOS for
shaping.
If you are only shaping through traffic on the box then you don't need
to use IFB at all. Just shape on local and wan facing IFs, this could be
an advantage in allowing the use of iptables eg. to mark/classify.
prev parent reply other threads:[~2014-07-06 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 10:27 PRIO qdisc traffic does not work as expected GGounot
2014-06-19 10:33 ` Andy Furniss
2014-06-19 11:42 ` GGounot
2014-06-19 13:58 ` Andy Furniss
2014-06-19 19:06 ` Dave Taht
2014-06-29 11:08 ` GGounot
2014-07-06 17:14 ` Andy Furniss [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=53B983F8.9030509@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.