From: Fred Stratton <fredstratton@imap.cc>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Correct syntax for cake commands and atm issues.
Date: Fri, 10 Jul 2015 12:13:24 +0100 [thread overview]
Message-ID: <559FA8D4.2030305@imap.cc> (raw)
I transitioned from ceroWRT to lupin, now at undisclosed version 4, to
try cake. I have a renown poor ADSL line, connected to TalkTalk. After
getting a 60 GBP discount by negotiating with a woman and her imaginary
Manager friend in Bangalore a month ago, I have no intention of moving
to fibre.
The wiki page gives insufficient detail.
I am currently using a bridged device to connect to the internet, and so
have a pppoe-wan interface on the WNDR3800. I do not use PPPoA ever.
Whatever options I use with cake, the flow is either raw, or atm
overhead is listed as 0.
I do not know what commands - or probably, more correctly, options - can
be used, and in which order
incoming
... cake bandwidth 11500kbit besteffort
can you add atm overhead 38 (does not work, returns 0)
or are besteffort and atm mutually exclusive? Do I need to use the term
'flows' somewhere?
do terms such as 'pppoe-vcmux; need to be preceded by 'atm'?
More clarity is needed, I suggest, or a man page equivalent.
On June 20th what I am experiencing was described by Alan Jenkins on the
cake list.
I note the latest posting by DT on this Cero-devel list apparently using
an ADSL line as a source example, only uses raw flows.
next reply other threads:[~2015-07-10 11:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 11:13 Fred Stratton [this message]
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
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=559FA8D4.2030305@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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