Traffic in correct queues but lower prior queues have too much "power"
-
Everything gets put into the correct queues but I feel like the lower priority traffic isn't subdued like I expected it to be. This is a 8Mbit/1Mbit DSL line where the actual bandwidth is at around 830kB/100kB, and I used these values when first creating the rules using the wizard. I'm using PRIQ scheduler.
If I start a download using a single connection in the P2P queue, wait till it reaches 800kB/sec, and then fire up a download from OthersHigh, everything behaves pretty much like you'd expect and P2P traffic gets put in its place, getting around 90kB/sec (though I'd like to see this even lower). The problem is that usually, the inbound traffic in the P2P queue consists of at least 30 connections, while downloads in OthersHigh are usually just a single connection and the P2P traffic won't budge below 600kB/sec.
Is this expected behaviour? My expectations going in was that as long as no one else is using the pipe, P2P could reign free, but as soon as there's a download in the higher queues P2P would get beat into submission.
-
Have you solved the problem?
I have the same problem: https://forum.pfsense.org/index.php?topic=74212.0
-
PRIQ doesn't rely on bandwidth specifications; all it cares about is higher priority packets go first. The traffic shaper UI treis to accommodate everything at once, but not all elements apply to all shapers.
Also, the traffic shaper isn't a limiter, so your queues will use up as much bandwidth as they can get while following the rules. If you have no action in your high queues, your low queues will zip along. When higher-class traffic appears, it gets priority, but the lower queues aren't throttled. If your P2P queue is still getting 600K/s, then it means that your higher queues are being properly serviced without impacting the P2P queue too much.
