From: Fred Stratton <fredstratton@imap.cc>
To: Rich Brown <richb.hanover@gmail.com>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated?/Not anymore...
Date: Fri, 27 Dec 2013 21:13:17 +0000 [thread overview]
Message-ID: <52BDED6D.2050203@imap.cc> (raw)
In-Reply-To: <12CCC35C-74F4-4F62-AF86-84AFD49A8093@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
The 'Enabled' checkbox is disabled by default.
I would have no problem with it being enabled by default, but would like
it retained.
I use a TP-Link device to bridge to the phone line. In the next year, a
build of OpenWRT will appear which I can apply to this, with all the
ceroWRT changes incorporated in it hopefully.
I envisage testing the operation of that device as a full gateway, and
using the ceroWRT device as an access point in the testing period, with
sqm partly or wholly disabled on it.
On 27/12/13 20:59, Rich Brown wrote:
>>
>> Probably didn't start sqm properly
>>
>> Restart it by hand via /etc/init.d/sqm restart
>>
>> tc -s qdisc show dev ge00
>>
>> Should show htb and fq codel.
>>
> Uh oh. PEBCAK (Problem Exists Between Chair And Keyboard :-)
>
> I see the problem... There's this little checkbox in the "Basic
> Settings" of the GUI... It's labeled "Enable" and hidden in plain
> sight above all the interesting stuff in that tab. If it isn't
> checked, the router is just as bloated as every other home router.
>
> However, if you *do* check it, everything works as desired. Whew!
>
> A few thoughts which might keep this from ever happening again:
>
> - Was it disabled by default? (I don't remember unchecking it...)
> - Is there even a reason to have the "Enable" checkbox? Would there
> ever be a circumstance where a person wouldn't want SQM?
> - Could the "Enable" checkbox be replaced by another "Not Enabled"
> entry in the "Interface name" dropdown?
>
> Thanks!
>
> Rich
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 4689 bytes --]
next prev parent reply other threads:[~2013-12-27 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 18:36 [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated? Rich Brown
[not found] ` <CAA93jw7oS-NsBVbzHHUyVKb=0yo-yX9h-j-okafvM2c=DBJwDA@mail.gmail.com>
2013-12-27 18:55 ` [Cerowrt-devel] Fwd: " Dave Taht
2013-12-27 19:10 ` Fred Stratton
2013-12-27 19:15 ` Dave Taht
2013-12-27 19:20 ` Fred Stratton
2013-12-27 19:25 ` Sebastian Moeller
2013-12-27 19:49 ` Dave Taht
2013-12-27 20:20 ` Fred Stratton
2013-12-28 0:07 ` Sebastian Moeller
2013-12-28 1:14 ` Dave Taht
[not found] ` <52BE494E.7010904@imap.cc>
2013-12-28 3:46 ` Fred Stratton
2013-12-28 10:33 ` Fred Stratton
2013-12-27 20:41 ` Fred Stratton
2013-12-27 20:59 ` [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated?/Not anymore Rich Brown
2013-12-27 21:13 ` Fred Stratton [this message]
2013-12-27 21:14 ` Fred Stratton
2013-12-28 0:10 ` Sebastian Moeller
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=52BDED6D.2050203@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@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