From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id B9B5321F112 for ; Wed, 22 Jan 2014 08:14:24 -0800 (PST) Received: by mail-qc0-f174.google.com with SMTP id x13so755377qcv.33 for ; Wed, 22 Jan 2014 08:14:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ps1ennisbZGeNvLt+bSEG+5WzdB8QVD9OSYSFhdCWRY=; b=FAeKxDEtUJr9kGrNHbW31siZRbi/L0Qk+yMH33XtlLv/bh4CuDaBQDXt2nzoejWstg MHlXqNArFEYCvcqFn4rapWxiDUP7MCbBMNKX3PjCYbL9fie71o1KnBoxcFNUH4OsqIed jyJmd36PbOBX2GEykKx6mfsCP+0bAP6pnSIiqXth5Nat9/LotPYTlkzGBeX/rQWWdDvE 2570n02lAnRcgo6Hwozk+q1TAhFgbceI63OrmvjOoNwY5rrJ7lRvjmO31N6VkZGhFnB6 p6cslFJkI5F3kPfsqHgV/Laa1+ZmwByl6+RvrY2gSlnd0x+lOL4vMmMGTaLr74MoA3io 50RQ== X-Received: by 10.224.136.195 with SMTP id s3mr1990747qat.95.1390396445736; Wed, 22 Jan 2014 05:14:05 -0800 (PST) Received: from richs-mbp-2505.home.lan ([64.223.225.159]) by mx.google.com with ESMTPSA id z8sm8419379qez.19.2014.01.22.05.14.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 05:14:04 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Rich Brown In-Reply-To: Date: Wed, 22 Jan 2014 08:14:01 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Dave Taht X-Mailer: Apple Mail (2.1827) Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] Final wording for CeroWrt SQM Pages (GUI and wiki)? 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: Wed, 22 Jan 2014 16:14:35 -0000 Dave, Thanks for this update. I think we're content with the = behavior/performance of the current code. My note was just obsessing = about the words that we present to customers who use CeroWrt. On Jan 21, 2014, at 11:06 PM, Dave Taht wrote: > On Tue, Jan 21, 2014 at 10:44 PM, Rich Brown = wrote: >> OK, I think we have consensus. I have modified the text of the = Setting up SQM page as described in the earlier messages = (https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-January/001997= .html) The wiki now says: = http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWr= t_310 >>=20 >> Next, the CeroWrt 3.10.26-2 GUI needs these changes: >>=20 >> - SQM tab heading needs to say "Smart Queue Management" instead of = "Active Queue Management" >=20 > done in the comcast build and for future builds. Great. > Incidentally, part of the appeal of "SQM" to me is the first hit is > for a fertilizer company. >=20 > http://steve.savitzky.net/Songs/mushroom/ >=20 > The song itself is kind of catchy (I don't know if he's online, I have > the CD) and can cause earworms on bad days. >=20 > "It comes from mushrooms, mushrooms, keep them in the dark..." :-) > I should also point out that multiple other schemes qualify as SQM in > my mind: gargoyle-router's ACC in particular, but also streamboost, > and qos-scripts, wondershaper, etc. >=20 > We could still use a brandname. I added a bit of text for the motivation for changing to the SQM note. I = can add a reference to Gargoyle-router, streamboost, qos-scripts.=20 Wondershaper? :-) >> - Change the text of the paragraph to say, "... and prioritization on = a single interface." >=20 > Not sure where this goes. Current comcast code says: >=20 > m =3D Map("sqm", translate("Smart Queue Management"), > translate("With Management\">SQM you " .. > "can enable traffic shaping, better mixing (Fair = Queueing)," .. > " active queue length management (AQM) " .. > " and prioritisation on one " .. > "network interface.")) Sorry for being telegraphic. I had meant the sentence to be more = explicit about the single interface. s/and prioritisation on one/and = prioritisation on a single/ >> - Basic Settings tab: we had discussed removing the "Enable" checkbox = and adding a "None" choice to the "Interface name" dropdown. Is this = possible? (default setting should obviously be "ge00") If not, the tab = is fine as-is. >=20 > Well this opens the problem of people wanting SQM on multiple > interfaces, which was a nice feature. Ahah. When I looked at the GUI, I thought it would provide this facility = only for the interface selected in the dropdown. Does the GUI handle it = for multiple interfaces? (I know that people can edit their scripts for = other interfaces.) >> - Queue Discipline tab is fine as-is. >>=20 >> - Link Layer Adaptation tab's dropdown lists three choices: >> - None (default) >> - ATM (almost every type of ADSL or DSL) >=20 > Is the () needed in the drop down I like it for the "None (default)" case, and we've used (default) in = other parts of the GUI. The ATM case is very wordy, though, but I figure = it's easier for people to see that they have DSL and choose it = (correctly). >> - Ethernet with overhead >=20 > in (PPoe? pppoa? what?) Yes, this is the bad case. What is technically true is "The choice that = is not ATM, but allows you to enter some additional overhead" Unless = someone has better wording, I say we stick with this until we find more = people who fall into this category, at which point we'll know more about = how to describe their situation. >> - Anything else? >>=20 >> It would be great to get these changes in the next build. Who can = make those changes? Thanks. >=20 > I note I'm burnt and just lost a week I could ill afford to this. I > have pushed out all sources in the hope > someone else can update the build howto and get something that = works.... As always, we appreciate everything you've done. I will be content if we = can make these changes to the GUI so we can focus our brainpower on = other matters. Safe travels. > I am travelling this weekend and won't have time to get another build = out. >=20 > Perhaps more cool stuff can land. I have a wishlist. :) >=20 > Perhaps someone can find a cure to the he problem but I fear it's > buried deep in a script or in ubus. >=20 >> Rich >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >=20 >=20 >=20 > --=20 > Dave T=E4ht >=20 > Fixing bufferbloat with cerowrt: = http://www.teklibre.com/cerowrt/subscribe.html