From: Sebastian Moeller <moeller0@gmx.de>
To: Jim Gettys <jg@freedesktop.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Any chance for the LUCI GUI for cake appearing?
Date: Fri, 26 Jun 2015 20:49:23 +0200 [thread overview]
Message-ID: <DB1EEED0-46CD-4000-BC3D-EDF65990975A@gmx.de> (raw)
In-Reply-To: <CAGhGL2CsB8A1CegU6AZ-SmE0oDaXL3bVCKN2CEMORYea_9Vm3A@mail.gmail.com>
Hi Jim,
On Jun 26, 2015, at 19:21 , Jim Gettys <jg@freedesktop.org> wrote:
> Inquiring minds would like to know….
I guess, that depends on your definition of “LUCI GUI for cake”; as far as I know you can select cake in the “Queueing Discipline” drop down in the “Queue Discipline” tab of luci-app-sqm. So if the machine has the cake module and a sufficiently recent (out-of-tree) tc binary installed it should just work. Using the “Advanced option strings…” it even should be possible to pass arbitrary strings to cake (without any error checking), so I assume we are all set up for cake testing (or should that be cake tasting?) from the LUCI GUI. But I have not managed to build cake locally, nor have I dared to risk my families internet connectivity by trying one of Dave’s newer "openwrt trunk with cake” builds. So these changes linger in the ceropackages-3.10 repository until we get enough tasting to convince Toke to pull them into the openwrt repositories (these changes affect both sqm-scripts and luci-app-sqm). Dave graciously allowed me access to one of his test machines, and the changes allow to set up cake from the GUI, but I only did limited functionality testing. (And we discovered that something was of in that cake worked but did not accept all the keywords it should have, but unless you are on a XDSL-Link you most likely do not care about specifying per-packet-overhead)
If you have any specific thing you are missing, let me know and I will try to help.
Best Regards
Sebastian
> - Jim
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-06-26 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 17:21 Jim Gettys
2015-06-26 18:49 ` Sebastian Moeller [this message]
2015-06-26 19:48 ` Dave Taht
2015-06-26 20:47 ` Sebastian Moeller
2015-06-26 21:04 ` Sebastian Moeller
2015-06-26 23:36 ` Jim Gettys
2015-06-26 23:58 ` Dave Taht
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=DB1EEED0-46CD-4000-BC3D-EDF65990975A@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jg@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox