From: Fred Stratton <fredstratton@imap.cc>
To: Jonathan Morton <chromatix99@gmail.com>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Correct syntax for cake commands and atm issues.
Date: Fri, 10 Jul 2015 14:11:57 +0100 [thread overview]
Message-ID: <559FC49D.7090505@imap.cc> (raw)
In-Reply-To: <CAJq5cE3f7uthRsHMEFHfJkXDEo7nSr7U4jKow0VWJkyGAZ4j+Q@mail.gmail.com>
I am using the latest version compiled by DT, after you last made this
incompatibility comment on the cake list.
I happen to have compiled separately a build with your changes of 22
days ago incorporated, but based on lupin undisclosed version 2. I shall
try that.
I am making an assumption throughout this that qdiscs should be used on
the WAN side always, effectively before the firewall. Is this assumption
correct?
On 10/07/15 13:57, Jonathan Morton wrote:
>
> You're already using correct syntax - I've written it to be quite
> lenient and use sensible defaults for missing information. There are
> several sets of keywords and parameters which are mutually orthogonal,
> and don't depend on each other, so "besteffort" has nothing to do with
> "overhead" or "atm".
>
> What's probably happening is that you're using a slightly old version
> of the cake kernel module which lacks the overhead parameter entirely,
> but a more up to date tc which does support it. We've seen this
> combination crop up ourselves recently.
>
> - Jonathan Morton
>
next prev parent reply other threads:[~2015-07-10 13:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 11:13 Fred Stratton
2015-07-10 12:57 ` Jonathan Morton
2015-07-10 13:11 ` Fred Stratton [this message]
2015-07-10 13:40 ` Jonathan Morton
2015-07-10 14:52 ` Fred Stratton
2015-07-10 15:16 ` [Cerowrt-devel] "Lupin undeclared"? Rich Brown
2015-07-10 15:39 ` Alan Jenkins
2015-07-10 23:16 ` Rich Brown
2015-07-25 12:48 ` Dave Taht
2015-07-10 15:19 ` [Cerowrt-devel] Correct syntax for cake commands and atm issues Alan Jenkins
2015-07-10 15:48 ` Fred Stratton
2015-07-10 18:25 ` Fred Stratton
2015-07-10 18:46 ` Sebastian Moeller
2015-07-10 19:14 ` Fred Stratton
2015-07-10 19:15 ` Dave Taht
2015-07-10 19:18 ` Jonathan Morton
2015-07-10 19:30 ` Sebastian Moeller
2015-07-10 19:27 ` Sebastian Moeller
2015-07-10 19:34 ` Fred Stratton
2015-07-10 19:40 ` Sebastian Moeller
2015-07-10 19:45 ` Fred Stratton
2015-07-10 19:49 ` Alan Jenkins
2015-07-10 19:50 ` Sebastian Moeller
2015-07-10 20:07 ` Fred Stratton
2015-07-10 20:12 ` Sebastian Moeller
2015-07-10 20:24 ` Fred Stratton
2015-07-10 20:34 ` Sebastian Moeller
2015-07-10 19:41 ` Alan Jenkins
2015-07-10 19:43 ` Sebastian Moeller
2015-07-10 19:17 ` Alan Jenkins
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559FC49D.7090505@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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