Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
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 23:04:19 +0200	[thread overview]
Message-ID: <C663E5D3-F612-4774-AA32-366A71005685@gmx.de> (raw)
In-Reply-To: <CAA93jw4h4mq4OAZwBiuf=gvXMA=1fAbdEuE4L7aOVbnK6P465g@mail.gmail.com>


On Jun 26, 2015, at 21:48 , Dave Taht <dave.taht@gmail.com> wrote:

> It turns out that I am pulling from openwrt for luci-app-sqm, not
> ceropackages, and overriding it was a headache. Fixed now, see below
> 
> router# cd /tmp; wget
> http://snapon.lab.bufferbloat.net/~cero3/luci-app-sqm_3-5_all.ipk ;
> opkg install ./luci-app-sqm_3-5_all.ipk
> router # /etc/init.d/uhttpd restart
> 
> if it breaks, you get to keep both pieces, but it worked for me, and
> yea! cake in the gui! thx sebastian!

	Too cite Shaggy “Wasn’t me” ;); the initial commit was not mine and I do not want to claim otherwise.  I basically just rearranged the "deck-chairs" as I tend to think. I seem to be better at the “ love for details”  thing than the”big picture”, anyways
Best Regards
	Sebastian

> 
> 
> I tried -
> 
> ./scripts feeds uninstall luci-app-sqm; ./scripts feeds install -p
> cero luci-app-sqm # seemed sane, did not work
> git rm in the feed itself did not work
> doing the uninstall, deleting the symlink, and the git rm, nuking the
> bin/ar71xx/packages/packages/luci-app-sqm*
> and doing a complete rebuild... eventually did work... but strikes me
> as a bit more brute force than I wanted.
> 
> I am not in a position (aformentioned build is my specialized for
> pico/nano build at the moment) to update the packages db,
> but I stuck up the correct new package... which you can install via
> 
> 
> Apologies for the confusion, I simply figured that the -p option would
> work, and never checked.
> 
> I also note that I think I am building things compile tuned for the
> archer mips34c, rather thanthe wndr3800´s 24c. However I kept the
> unaligned access hacks (not needed on the 34c derived archer, but
> needed on the 24c wndr3800)
> 
> Sigh.
> 
> maintaining 3 separate trees for the platforms we sort of support is a
> PITA. Then adding in something that can mesh by default on 2 others.
> and then trying to get anything to compile for another arch entirely
> and failing...
> 
> 
> On Fri, Jun 26, 2015 at 11:49 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> 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
>> 
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 
> 
> 
> -- 
> Dave Täht
> worldwide bufferbloat report:
> http://www.dslreports.com/speedtest/results/bufferbloat
> And:
> What will it take to vastly improve wifi for everyone?
> https://plus.google.com/u/0/explore/makewififast


  parent reply	other threads:[~2015-06-26 21:04 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
2015-06-26 19:48   ` Dave Taht
2015-06-26 20:47     ` Sebastian Moeller
2015-06-26 21:04     ` Sebastian Moeller [this message]
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=C663E5D3-F612-4774-AA32-366A71005685@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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