HFSC per session limit
whitediode last edited by
Iam still a bit newbie to pfsense, so if iam wrong correct me
in 2.0-ALPHA-ALPHA ( built on Wed Sep 23 11:28:05 UTC 2009 ) the hfsc traffic shaper upper-limit parameters ( m1, d, m2 ) used to limit traffic per session, that if session started ( new connection ) it can have m1 KBytes for d miiliseconds then it will not take more than m2 KBytes for the remaining time, and if another session ( belongs to the same queue ) started it used to take the same m1 KBytes for d miiliseconds ( although the previous session is still getting m2 Kbytes only ) , this behaviour was so useful and fair , and i thought that this is what hfsc was all about.
But now in pfsense 2.0-BETA hfsc upper limit doesn't work per session biases ( as i tested it ) if a session started with its m1 KBytes for d miiliseconds then get limited to m2, any new session starts; gets only m2 directly, even if this session was from another ip ( but belongs to the same queue of course ).
i just wanted to know if this is a bug or this is the normal behavior,
Thanks very much