The point of QoS is NOT to have the queues build up, not use all the bandwidth, so if you keep accepting packet at the maximum rate (and thus increasing latency for incoming packets), it's already to late to do shaping, the packets already arrive with a delay. You can't control what packets are sent to you directly.

You can manage and control bandwidth through conference manager application. This will allow the minimum bandwidth required for video conferencing and will not make the whole system busy

So it reaches 100% CPU?  ??? If so, polling might help: http://blog.pfsense.org/?p=115

Thank you!  That makes complete sense to me now.

Maybe you want to change to PRIQ and put your game (and VoIP maybe?) in highest priority together with the ACKs?

Sorry to dig up an old thread… In my case where I am running 1.2.3 and experiencing the same problem, I can get the up packets to go into the qvoipup if I remove the tos_audio=ef line in asterisk.  But I'm wondering if this is the proper way to resolve this particular qos issue?  Or are there any other suggestions short of going back to 1.2.2? Thanks in advance

You might want to read the pfSense book then.  The traffic shaper works fine in 1.2.3 but you have to configure it correctly.

hi, again… i just cant get this thing to work... have managed WAN, LAN, WIFI (third NIC + wifi router) works all great.. but i want to manage bandwith for WiFi and all i get are errors... Is the error on my side ? doing someting wrong? or are there some bugs? Sorry...im not an expert..but really love this PF Sense :P Any help?

All the created rules are settled at "floating" rules. What i did (maybe silly), was creating aliases for the specific ports and reduce the amount of rules here. Looks better and is easily to maintain.

sorry i was away for a while thanks ryn24, for the reply, i would really apreciate that. hadi57

@FixMaster: But when i check at Traffic Graph, It download 300kbps (Means he got 3 Mb line) Actually, I want to point out that this is not true. 300 Kb = .3Mb. 1000 Kbit = 1Mbit.

It won't matter in this case.  ToS is useful for prioritizing traffic before putting it onto a slower link.  It is not very likely that the T1 is actually faster than your LAN setup, so I can't see this making any difference whatsoever.