Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: cerowrt-devel@lists.bufferbloat.net,
	Jonathan Morton <chromatix99@gmail.com>
Subject: Re: [Cerowrt-devel] Correct syntax for cake commands and atm issues.
Date: Fri, 10 Jul 2015 15:52:40 +0100	[thread overview]
Message-ID: <559FDC38.9010400@imap.cc> (raw)
In-Reply-To: <CAJq5cE3f7uthRsHMEFHfJkXDEo7nSr7U4jKow0VWJkyGAZ4j+Q@mail.gmail.com>


You are absolutely correct.

I tried both a numeric overhead value, and alternatively 'pppoe-vcmux' 
and 'ether-fcs' in the build I crafted based on r46006, which is lupin 
undeclared version 2. Everything works as stated.

On lupin undeclared version 4, the current release based on r46117, the 
values were not recognised.

Thank you.

I had cake running on a Lantiq ADSL gateway running the same r46006 
build. Unfortunately this was bricked by attempts to get homenet 
working, so I have nothing to report about gateway usage at present.



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
>


  parent reply	other threads:[~2015-07-10 14:52 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
2015-07-10 13:40     ` Jonathan Morton
2015-07-10 14:52   ` Fred Stratton [this message]
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=559FDC38.9010400@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