Add me to the list that can't get this to work. Anyone have any ideas? If I use PRIQ, it appears to work, but I need a little more control.

I wonder if I should have asked this in the firewall forum. Bump?

Correct. I was just using the wizard's terminology.

The wizard tries to be one size, fits all GUI, and that's why you see references to priority when creating an HFSC shaper.  HFSC doesn't deal in priority levels, only bandwidth allocation.

Thanks jahonix, just tried turning strict off via that link and no change.
Might have to retreat back to 2.1.5 anyways, openvpn is proving too flacky with my devices.

Edit:
Due to time constraints I have gone back to 2.1.5, I have not given up on 2.2 but will tackle this and my openvpn issues at a later day. Thanks you developers for your awesome backup and restore utility this was fun adventure, so no complaints from me. Thanks again for all who read and tried to help me figure it out.

Thank you Harvy66, we will try this and let you know.

Working again…. Re-installed pfsense 2.1.5 and restored the backup. All fine now.
I think the upgrade from 2.1.4 to 2.1.5 broke the limiter somehow.

Tell him you have figured out how to limit it to no more than 10,000,000 or some number you estimate you wont exceed.

Lie - They do it all the time.

I've just went thru the wizard using CBQ and input my allworx servers public IP in the SIP ip box, and these are the shapes it created, however it seems I'm missing the IP address from the voip floating firewall rule. Any idea why?

blah.jpg
blah.jpg_thumb
Untitled-4.jpg
Untitled-4.jpg_thumb

It's designed to accept traffic for intra-router forwarding, like LAN to DMZ.  You probably don't want to shape it much at all.  The bandwidth should basically be the link speed. (100M, 1G, etc) which it gets from the interface link speed if left unspecified, I believe.

I have qLink as the default queue.  If I don't put the traffic in another queue, let it rip.

Increase your queue lengths. They default to 50. I have my high bandwidth queues, like web browsing, in the 5,000 length range, or 2,500 for less bursty traffic, but I have 50mb.

I also use the "codel" queue management for each queue, except for queues that shouldn't drop packets. It drops packets based on time spent in queue with a target of 5ms or less. I don't know how PFSense has it implemented, but if it's implemented to spec, just set the length to something long enough and use codel.

I hear what you're saying, but I was certain that jimp told me last summer that the PRIQ didn't use the bandwidth value at all.  I don't know how the internal buffering is done.

Thanks all for the responses.  I switched over to PRIQ but I'm having issues where it's not playing nice with the priority.    I hate to be one of those people who asks yet another 'why isn't it working' question, but I"m going to be because it's driving me up the wall.

I'm going to create another topic though since it wasn't the intent of hte original posting.

Thanks!

Another minor note. I noticed my download was getting up into the 50/51mb range, which was strange because PFSense is really really good at keeping the bandwidth within the desired amount. I assume it was because I had my interface set to 1gb, and while my upper limit was set to 48, all "real time" bandwidth is taken from the root node, this would mean the total bandwidth consumed would be UpperLimit+RealTime.

I adjusted my my LAN interface to be 48Mb and it seems to be keeping a tight limit to just under 48mb now. To make sure my traffic shaping didn't conflict with managing PFSense, I just opened up my port on my admin vlan.

I just thought this may be helpful to someone at some point.

I'm not aware of anything in pfSense that would disable an interface based on some threshold.  There are a couple of dashboard widgets that will show you the traffic totals, but I don't know how often they reset and there are no configuration options.  Status - RRD Summary (an add-on package that is not installed by default) gives details & totals per interface and starts at the first of the month.

Hi had the same problems many times before with limiters. I don't think it's browser related. I use chrome all the time. Limiters handling seems to be unstable sometimes.

To modifie one existing limiters I have to delete them and recreate them all in order to get them working properly.

Also, you need to limit your upload/download to lower bandwidths, otherwise your current setup has virtually no effect.

I pay for 6mbit/768kbit ADSL, but my real-world upload is ~666kbit. For proper QoS (so you can control latencies by avoiding any buffering at the ISP), you need to limit your upload to something below your real-world upload. I use 600kbit, in my case.

I know it is unfortunate, but to properly employ QoS, you will need to do some more research. I had to… I have been crashing down this rabbit-hole for months. :)

Here is a good introduction, in my opinion.
http://www.linksysinfo.org/index.php?threads/qos-tutorial.68795/