First: You must have pf 1.2.3 Final Realease - not 1.2.2!
Second: Use Traffic Shaper wizard again and then delete(disable) unused rules. Don't check "Random Early Detection In and Out". Settings created by Wizard's are TRUE . Don't change their unnecessarily. That's all.

Great, will try that and post back, thanks a lot  :)

PRIQ has this limitation as part of its algorithm.

I will try to teach the GUI about this so people get a reasonable message.
Otherwise there is a limitation of 4096 iirc on other algorithms.

You can make a WAN rule with a destination of the LAN IP involved (NAT happens before the rules are processed) or you could put a rule on the floating tab, on lan, in the 'out' direction.

Need a pictorial representation of your setup for a more complete answer.

The short of it is:  Catch your VOIP traffic by using the IP address of the Asterisk server in the rules.  Catch your OVPN traffic by using the destination port (address as well if both sides have static IPs).

Adjust your TBR size for starters.  This will prevent large downloads from hogging the line.
If using Squid, look under Bandwidth management, you should be able to set it to throttle by extension or throttle per HOST.  The former will allow you to target downloads specifically without throttling webpages (the content might be affected if you don't do up the extensions properly).

Funny, I've got just the same question, after an otherwise totally smooth upgrade from 1.2.3 to 2.0-RC1.  I tried walking through the traffic shaper wizard last night, and wound up cutting my throughput in half … so I disabled the shaper until I could tailor it to my VOIP setup more accurately.

I haven't gone rooting around in the 2.0 docs to see if there's a how-to.  I'm guessing there must be, somewhere.

Thanks, sounds like it's just the thing. Time to go off and have a poke around…

I tried to change the port assuming that since there isnt a rule to block it then it should work but for some reason no matter what port I try to make it, I can only connect on port 80. When I go back it shows in the webui that the new port is still in the settings but not working…..

anyone have any ideas?? thanks.

Update
So I tried to do it and I think its working ..... I took. Had to restart to get the new http port to become active. Then ended up reinstalling squid because it was complaining about some bogus setting. So did that and now everythings running but I still dont have qOthersDownH in my queues. I have:
qwanRoot
  qwandef 
qwanacks 
qVOIPUp 
  qPenaltyUp 
qlanRoot 
qlandef 
  qlanacks 
qVOIPDown 
qPenaltyDown

I used the defaults from the wizard but setup a penalty box, voip priority and thats it
any ideas?

Hi,

Did you change the priority of DNS in the wizard? I noticed (months ago, also with 2.0) that DNS request from my pfsense box to external NS servers does not work if I set the priority of DNS to high in the wizard. Never got an answer why this happened?

Thank you very much!

I have ended up flashing my slingbox back to factory code.  I then moved the connection directly to the firewall on a switch that was directly connected.  It connect at a odd speed just like my vonage device which runs at 10/half.  Now it is working fine.  I still would like to setup QOS for this to give it higher priorty so we don't have so much lag.
RC