From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id AA374201B88 for ; Wed, 22 Jan 2014 11:18:40 -0800 (PST) Received: from hms-beagle-3.home.lan ([217.86.112.208]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M4B71-1VGHug0KMV-00rqdI for ; Wed, 22 Jan 2014 20:18:37 +0100 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: Date: Wed, 22 Jan 2014 20:18:38 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5AAC738E-CA77-4533-B52B-E4F4EDC1505F@gmx.de> References: To: Rich Brown X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:qd5OdDxW5zLVD2+MUksU3c4IGcaQnl6ZNj/n1ogFa2rOdbzRdj6 bckp+0lKzGRcgvL6rTu29zJlIaCrlk/5Rm2LZQsABLhF6l1ubW/yXZM0fdd00G6MeYIApj2 hgWHw6CukwSsSZSK6tdSeXWxJO3DQ4bWuTjqbKS+iOVdv4fydJIdBJKLN2fyniOkWRlQqNS R+9G18r2QCDIIuyt2r7KQ== 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 19:18:41 -0000 Hi Rich, hi Dave, On Jan 22, 2014, at 14:14 , Rich Brown wrote: > Dave, >=20 > 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. >=20 > On Jan 21, 2014, at 11:06 PM, Dave Taht wrote: >=20 >> 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. >=20 > Great. >=20 >> 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..." >=20 > :-) >=20 >> 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. >=20 > 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 >=20 > Wondershaper? :-) >=20 >>> - 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.")) >=20 > 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/ >=20 >>> - 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. The interface list box is populated by a bit of code, not sure = how easy it is to include none here. >>=20 >> Well this opens the problem of people wanting SQM on multiple >> interfaces, which was a nice feature. >=20 > 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.) Curently the GUI only allows to instantiate SQM on a single = interface, but it used to be possible to configure more with the GUI = (but since I never tested these I disabled that ability for the time = being; reasoning if we expose this it should be tested). >=20 >>> - Queue Discipline tab is fine as-is. This probably will grow a few additional fields in the advanced = or dangerous section, to expose limit and target and interval (for those = qdiscs that support those). But this is not urgent... >>>=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 >=20 > 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). I see, I thought rather err on the verbose side here, but "ATM: = for ADSL links" would do nicely. I would like to avoid DSL here as this = typically encompasses ADSL, VDSL, and sometimes even SDSL, and we really = only need this for all ADSLs and potentially a few VDSLs. >=20 >>> - Ethernet with overhead >>=20 >> in (PPoe? pppoa? what?) >=20 > 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. "Ethernet: for non-ATM links with additional overhead" this = includes for example PPPoE overhead (seen on VDSL, and sometimes fiber), = VLAN overhead (seen on VDSL and sometimes fiber), and what have you. = Note PPPoA users need to select "ATM" instead as the oA stands for "over = ATM".=20 So to sum up is the following acceptable for all: "None (default)" "ATM: for ADSL links" "Ethernet: non-ATM links with overhead" Please let me know the what you all prefer and I check the consensus in = (I really have lost track on what the current proposal was=85) Best Regards Sebastian >=20 >>> - 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.... >=20 > 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. >=20 >> 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 >=20 > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel