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/

The GUI page runs that same command in a loop, it's not as "real time" as it might seem.

There's no way I know of to sort that data at the moment.

I've follow this tutorial
https://forum.pfsense.org/index.php?topic=63531.msg364520#msg364520

And now when I download from 2 differents PC they got each one half bandwidth, the same for more PC. Getting close to resolve the problem!

Still can't figure out why the traffic shapping give the same speed even if one queue is 1% share and the other one 61%.

PS: I've got the last build:
2.1.5-RELEASE (amd64)
built on Mon Aug 25 07:44:45 EDT 2014
FreeBSD 8.3-RELEASE-p16

It was a fat finger error on the rule that catches qAck.  Everything works as advertised.

It's not "unfixable", it's just not easy to fix and has never worked so it got pushed off to a future release. As I stated in the linked bug report, there is no "quick solution". If there was, it'd be fixed in 2.2 already.

What happens if you disable your L7 rules?

maybe you could try to limit it based on ip addresses. Maybe this thread could help. I am also new to pfSense just trying to help.

https://forum.pfsense.org/index.php?topic=63531.0

Just to give an update on this…

I am running pfSense 2.2 RC1, and it appears this is working now. I'm a happy camper.  :)