@jimp Thx !

I moved your post - it sure wasn't anything to do with forum feedback. Also - running 2.1.1 of pfsense.. If you want help with anything your going to need to be current.

Ah, that makes sense. Thanks!

Wow, thanks for taking the time! I'll do this as soon as my wife stopped using instagram... don't want to slow her flow ;)

@Binson_Buzz Glad that helped. The people behind the package did an awesome job. It checks many boxes and does them all so well. That's why it's so easy to recommend.

you can inbound shape + fq_codel to 85-90% of the isp rate.

You're using HFSC. You can't do both bandwidth shaping and priority shaping, they're fundamentally pretty much exclusive. What you can do is set the bandwidth on each queue and HFSC will make sure each queue gets the correct amount of bandwidth. For example. At one point I had a 64Kbit/s queue for ICMP traffic with HFSC. Even when P2P traffic was using 99Mb/s of the 100Mb connection, I could get a ping that acted as if the connection was idle because HFSC would always make sure ICMP got 64Kbit/s.

@harvy66 Thanks. Are you suggesting that I adjust the "mask" within the limiter? Mask: Destination address IPv4 mask bits: 32 (?) If I did that, then that sounds to me like it is a limiter pipe per outbound destination - meaning that each outbound connection gets the 10Mb cap. (?) I'll review in the online book for pfSense and read up more on it. Thanks

I also have the same question. I tried placing some floating rules at the bottom of the list, but the packet counts aren't going up nearly fast enough to be matching the dpinger traffic.

Sorry for my ignorance. Solved this problem. it was going trough the voip queue and as i looked in voip queue settings, bandwidth was 32kilo bits. damn.

hello sir how to add traffic data limit Quota(1GB,5GB....) as per ip client..

There are theoretical TCP throughput limits based on RTT and window size. That calculator does a pretty good job at estimating what can be an expected maximum.

Wow, no responses yet. I'm not sure how to do this, but I am curious what traffic is being created by pfSense. IPv6 is not that common yet, shame. Possible there is a bug, but pfSense tends to do very well following the standards and best practices. Rule of thumb is that if something is going wrong, it's not the fault of pfSense. Any packet dumps of what the traffic is and how much?

Try disabling ECN? Since we're talking about uploading P2P traffic, are you sure that it wasn't just a coincidence of timing that you had less bandwidth going out? Did you toggle it on/off and see it going up and down reliably each time?