News: This forum is now permanently frozen.
Pages: [1]
Topic: Dynamic QoS priority  (Read 5893 times)
« on: February 26, 2011, 19:20:24 »
awesomechairs *
Posts: 4

I've noticed in the Tomato firmware for Linksys and Buffalo routers that there's an option to dynamically change the QoS priority according to the amount of traffic transferred.

For example, if an http download is less than 1MB, the priority will remain at the level that applies to all http traffic (say, high), but if the download transferred over 1MB (say, downloading an ISO file), the http request would be downgraded to a lower QoS priority (say, low).

Would this be considered as a feature of monowall, or does it defeat the small footprint idea of the distro?

Would you care for some tea?
« Reply #1 on: February 27, 2011, 14:43:05 »
Omerik *
Posts: 35

There is somewhere else, in this forum, a discussion like this.
http://forum.m0n0.ch/index.php/topic,4811.0.html#msg14822

It look like that m0n0wall doesn't has a dinamic "adjustment" of the bandwith according to the size of the download.

There is a traffic shaper which adjust the limit of the bandwith according to the "position" in the networks of the m0n0wall You're using. I mean, each IP has his bandwith allocation.

I believe that someone has request to the admin to add this feature in the future.
« Last Edit: February 27, 2011, 15:29:23 by Omerik »

There's no a second possibility to make a good first impression.

Euro Buchberger
« Reply #2 on: May 06, 2011, 14:26:22 »
Јаневски ***
Posts: 153

I am wondering if it could be done in some way by using the data from the connection states table.

For example:
1) There is a script that runs every 60s or 120s checking if the connection state's transferred data size is more or equal than xB, if so a traffic shaper rule is applied, else nothing happens.

2) In order to avoid using dynamic traffic shaper database, another script runs every 3600s and removes all traffic shaper rules thus removing the limitation.
If the user continues to download, then the limit would be set again in maximum 60s or 120s depending on the first script execution interval setting.

3) The dynamic shaper is on/off switchable by using the webGUI.
All script execution times have default values however the user could redefine them,
the pipes are also editable.

*Avoiding short intervals would decrease CPU load.
« Last Edit: May 06, 2011, 14:36:50 by Јаневски »

 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines