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'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.
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
Thanks for the response. I ended up actually just reinstalling since I was just getting started. It might be nice to have in future versions a "reset to defaults" button for certain packages….like snort. :)
I have a 50/50 connection and I had to up my queues to 2500 to avoid dropped packets because of micro-bursting. You may want to try something smaller, but give 200 a try and see if it makes a difference in your throughput.
There are diagrams in the 2.1 book. I'm not exactly sure where floating rules come in.
Here's one paste. I am operating on the assumption that a floating rule on WAN out pushes the firewall rules on WAN back into the path and that's the proper order. LAN rules, then floating on WAN out for outbound states.


@KOM:
No idea. I don't use captive portal.
Maybe i'm the only one to use captive portable with the traffic shapping.
I'll continue my research.
Thanks.
If all of your rules don't have a fixed upperbound, there should be a way to change the root to increase its upper limit. I'm not sure how, but there's bound to be a way.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.