From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 72C0121F0E7 for ; Fri, 27 Dec 2013 13:13:21 -0800 (PST) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 53520208B9; Fri, 27 Dec 2013 16:13:19 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 27 Dec 2013 16:13:19 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=imap.cc; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type; s=mesmtp; bh=KQrawukxo/J67Zg0/Pc8iONk O78=; b=iXGrN6WwDuANea/qR0Ci0nARQsDjYEU+MJ/DcKFd1n08gNzyi3szYtT5 tE3pr0Cd1/FtIPlUw5NzEgX51jgHTmPNMNsBAX3M7gxDRCFLxq0LiwwxX3h2vrGA 0GTO688L3/t1ZlzinnWgkzzyV0W/y2S5JfnDRNUKopyjqU11Jkg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type; s=smtpout; bh=KQra wukxo/J67Zg0/Pc8iONkO78=; b=US6tLJHgAcL3kBNa0qW6vcn6QgtwFj3aM3RI MgyO8nWAXUbbNfgZXA3VszDP9G/7bO1xmNrr0z6crr7JNcTx7LRMiGAgr02hXA2w 2dFRiO6OBmH9jqTYoJVd+pLrERXL2PDBe3G2TNEsFw0VYLqHzJPyY0+ObWh+pNH7 c//jCBs= X-Sasl-enc: sIC5mj8QnpB0YLgFNlbP2Nq+6v3LDues31Q8Yj5dXXAU 1388178798 Received: from [172.30.42.8] (unknown [2.99.243.63]) by mail.messagingengine.com (Postfix) with ESMTPA id B70146800F7; Fri, 27 Dec 2013 16:13:18 -0500 (EST) Message-ID: <52BDED6D.2050203@imap.cc> Date: Fri, 27 Dec 2013 21:13:17 +0000 From: Fred Stratton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Rich Brown , cerowrt-devel@lists.bufferbloat.net References: <571C0EE5-DC15-4A9C-A195-A97F93A335EB@gmail.com> <12CCC35C-74F4-4F62-AF86-84AFD49A8093@gmail.com> In-Reply-To: <12CCC35C-74F4-4F62-AF86-84AFD49A8093@gmail.com> Content-Type: multipart/alternative; boundary="------------010100060801010201080903" Subject: Re: [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated?/Not anymore... X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 21:13:21 -0000 This is a multi-part message in MIME format. --------------010100060801010201080903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 --------------010100060801010201080903 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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

--------------010100060801010201080903--