* cbq.init module is already available (http://sourceforge.net/projects/webmin-cbq)
Why: You start a download that can't be throttled within the application (such as a mozilla .xpi, kazaa, or something else). This eats up all your bandwidth so that everyone else using your adsl (for example) can't use the connection. ssh / telnet sessions are also ruined.
But cbq is quite compilcated and all the cbq.init module really does is provide an interface that is much like using ssh.
A GUI that sets up priorities for bandwidth via the prio or htb chain would be great. This could be built using htb.init. Instead of limiting htb.init reorganises so that bandwidth is only limited when needed.
* cbq.init module is already available (http://sourceforge.net/projects/webmin-cbq)
Why: You start a download that can't be throttled within the application (such as a mozilla .xpi, kazaa, or something else). This eats up all your bandwidth so that everyone else using your adsl (for example) can't use the connection. ssh / telnet sessions are also ruined.
But cbq is quite compilcated and all the cbq.init module really does is provide an interface that is much like using ssh.
A GUI that sets up priorities for bandwidth via the prio or htb chain would be great. This could be built using htb.init. Instead of limiting htb.init reorganises so that bandwidth is only limited when needed.
htb.init - http://sourceforge.net/projects/htbinit/
The prio chain would be a simpler method of controlling bandwidth too.
In the GUI the following features would be handy -
- limit by source IP
- limit by destination IP
- limit by source PORT
- limit by destination PORT
+ able to put these rules in order of priority
I favour an interface to the prio chain since it's simpler but since the htb.init script exists you may want to use that.
Interested?
pps: here's a link to a company selling this functionality on CD for $159 (http://www.bandwidtharbitrator.com/)
and perhaps limiting optionally specified as a percentage % ?