How linkshare and real-time works?
-
Hi everyone, sorry about my poor english,
This is my first post here, i'm testing Pfsense 2.0 Traffic Shaper feature, i already read the chapter of the pfsense book about traffic shaping as well some wiki documentation and some forum posts but, i still don't very well how "real-time" and "Linkshare" works!
i don't understand why when i put a value of 50Kb in m2 linkshare, using a limit of 400Kb of Download, this queue reaches more than 50Kb of download, even if there are other queues with higher priority downloading something.
can someone help me please? ???
-
This information is taken from this link…Please reference for further information: http://calomel.org/pf_hfsc.html
realtime: the amount of bandwidth that is guaranteed to the queue no matter what any other queue needs. Realtime can be set from 0% to 80% of total connection bandwidth. Lets say you want to make sure that your web server gets 25KB/sec of bandwidth no matter what. Setting the realtime value will give the web server queue the bandwidth it needs even if other queues want to share its bandwidth.
upperlimit: the amount of bandwidth the queue can never exceed. For example, say you want to setup a new mail server and you want to make sure that the server never takes up more than 50% of your available bandwidth. Or lets say you have a p2p user you need the limit. Using the upperlimit value will keep them from abusing the connection.
linkshare (m2): this value has the exact same use as "bandwidth" above. If you decide to use both "bandwidth" and "linkshare" in the same rule, pf (OpenBSD) will override the bandwidth directive and use "linkshare m2". This may cause more confusion than it is worth especially if you have two different settings in each. For this reason we are not going to use linkshare in our rules. The only reason you may want to use linkshare instead of bandwidth is if you want to enable a nonlinear service curve.
nonlinear service curve (NLSC or just SC): The directives realtime, upperlimit and linkshare can all take advantage of a NLSC. In our example below we will use this option on our "web" queue. The format for service curve specifications is (m1, d, m2). m2 controls the bandwidth assigned to the queue. m1 and d are optional and can be used to control the initial bandwidth assignment. For the first d milliseconds the queue gets the bandwidth given as m1, after wards the value given in m2.