<br><div class="gmail_quote">On Fri, Jun 7, 2013 at 1:34 PM, Will Hawkins <span dir="ltr"><<a href="mailto:hawkinsw@opentechinstitute.org" target="_blank">hawkinsw@opentechinstitute.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06/07/2013 01:11 PM, Ben West wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is the thinking here along the lines of building UI elements on top of<br>
the QOS implementation already provided via qos-scripts and<br>
luci-apps-qos? Or an entirely new OOS implementation?<br>
<br>
If you're looking at an entirely new OOS implementation, a possible<br>
difficulty is that OpenWRT AA has adopted bleeding edge kernel versions<br>
obsolete certain methods typical to older QOS implementations. Most<br>
recently in a thread on this list, the departure of IMQ from the kernel<br>
layer rendered the bandwidth throttling features of the nodogsplash<br>
captive portal inoperative.<br>
</blockquote>
<br></div>
Would you mind sending a link to any information you have about IMQ inclusion/removal from the kernel? I'm just curious is all!<br>
<br></blockquote><div><br>Here is what I've found about it. IMQ no longer exists in Attitude Adjustment or trunk, to my understanding.<br><br><a href="http://wiki.openwrt.org/doc/uci/qos">http://wiki.openwrt.org/doc/uci/qos</a><br>
<a href="https://forum.openwrt.org/viewtopic.php?id=28947">https://forum.openwrt.org/viewtopic.php?id=28947</a><br><a href="http://wiki.openwrt.org/doc/howto/packet.scheduler/packet.scheduler?s[]=imq#required.packages">http://wiki.openwrt.org/doc/howto/packet.scheduler/packet.scheduler?s[]=imq#required.packages</a><br>
<br>The actual changeset removing imq:<br><a href="https://dev.openwrt.org/changeset/25641/trunk">https://dev.openwrt.org/changeset/25641/trunk</a><br><br>Preferred replacement implementations should use IFB:<br><a href="http://www.linuxfoundation.org/collaborate/workgroups/networking/ifb">http://www.linuxfoundation.org/collaborate/workgroups/networking/ifb</a><br>
<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Will<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
Do you know what kernel version EasyTomato is bundling? I believe<br>
Tomato itself is still wedded to kernel v2.6 (or older?) and<br>
unfortunately fully obsolete for the topic at hand.<br>
<br>
Besides all that, it may just be simplest to encourage the end user to<br>
input their overall Up/Down bandwidth values into any QOS admin UI form,<br>
rather than having the node itself try to determine that. It could be a<br>
basic step like "connect your laptop directly to your Internet<br></div>
connection and run <a href="http://speedtest.net" target="_blank">speedtest.net</a> <<a href="http://speedtest.net" target="_blank">http://speedtest.net</a>> a few times ..."<div class="im"><br>
<br>
On Fri, Jun 7, 2013 at 8:08 AM, Seamus Tuohy <<a href="mailto:s2e@opentechinstitute.org" target="_blank">s2e@opentechinstitute.org</a><br></div><div><div class="h5">
<mailto:<a href="mailto:s2e@opentechinstitute.org" target="_blank">s2e@opentechinstitute.<u></u>org</a>>> wrote:<br>
<br>
Hello All,<br>
<br>
I dropped development on a user interfacefor the QOS work a few weeks<br>
ago and I wanted to give an update in case anyone wants to take it on in<br>
the future.<br>
<br>
Looking at various interfaces I think that modifying the Tomato<br>
interface for QOS <a href="http://www.easytomato.org/features/scheduled-rules/" target="_blank">http://www.easytomato.org/<u></u>features/scheduled-rules/</a>,<br>
which is based on the Toastman version of Tomato<br>
<a href="http://linksysinfo.org/index.php?threads/toastman-releases.36106/" target="_blank">http://linksysinfo.org/index.<u></u>php?threads/toastman-releases.<u></u>36106/</a>, is<br>
the best option for implementing QOS on Commotion. It is currently built<br>
for DD-Wrt, but looking at the scripts it mainly creates TC files, and<br>
as such, would be an easy enough lift to move over to OpenWRT and LuCI.<br>
Though, there will be some extra work fiddling with multiple zone rules.<br>
<br>
Below is some useful info from William Dixon at Easy Tomato that I<br>
thought would be useful to append to this if anyone wants to continue<br>
this work.<br>
<br>
"One of the really hard parts of this is to automatically figure out<br>
your connection speed without constantly blasting huge amounts of data<br>
over the network (you need your speed for QoS settings and they can<br>
fluctuate a lot during a day). There are a few ways to do it, but its a<br>
lot of work, but really needs to a grad research project. We were<br>
hoping research group at GaTech would do it for us, but that's looking<br>
less likely.<br>
<br>
This is<br>
long<<a href="http://www.linksysinfo.org/index.php?threads/using-qos-tutorial-and-discussion.28349/" target="_blank">http://www.linksysinfo.<u></u>org/index.php?threads/using-<u></u>qos-tutorial-and-discussion.<u></u>28349/</a>>,<br>
but a very good overview of how QOS stuff works. It takes a LOT of<br>
fiddling to get it really sail (and more dangerously, some<br>
counterintuitive settings), but once it does, it's awesome! We got a<br>
hospital with 100 computers to go from website timeouts to skype calls<br>
with a single router!"<br>
<br>
<br>
s2e<br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br></div></div>
<mailto:<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.<u></u>chambana.net</a>><div class="im"><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
<br>
<br>
<br>
<br>
--<br>
Ben West<br>
<a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br>
</div><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a> <mailto:<a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a>><br>
<a href="tel:314-246-9434" value="+13142469434" target="_blank">314-246-9434</a><div class="im"><br>
<br>
<br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
314-246-9434<br></div>