QoS/Traffic Shaping Issue
Just wondering if anyone else has noticed an issue with traffic shaping turned on for connections above 300Mbps?
We had 150MbpsX15Mbps until yesterday and it has worked flawless.
After getting an connection Upgrade to 500MbpsX20Mbps, I re-ran the wizard to adjust for this change.
Sadly it would seem 288Mbps seems to be the limit when Traffic shaping is turned on.
With it turned off we get the full 500.
I have tried deleting and re-creating the traffic shaping rules, with no change.
The reason we require traffic shaping is mostly on the uplink due to it being fairly limited, and the need to protect VoIP service.
Is there a known bug, or am I missing something that someone can shed some light on?
Intel Core 2
@koreyb Update: The wizard appears to be creating qLink which was the cause of the 300 Mbps limit on the downlink. I disabled qLink and the limit disappeared. Does this mean the wizard may need an fix applied?
qLink is created on the LAN side by default. It's a percentage of the total ...the wizard creates a bunch of things as a percentage of the total bandwidth entered, though some are % and others Kbit/s. Did qLink have "Borrow from other queues when available" checked as mine does? qLink should be underneath LAN which is the limit.
I have read somewhere that Netgate recommends 1) using the same units for all rules (e.g. Mb/s or Kb/s or %), and 2) using even numbers (1 Mb/s not 1.0234 Mb/s), so I usually go through and change them all after the wizard creates them with a mix of Kb/s and percentages. But I've not run into a situation where the default was throttled by something less than what I entered for download/upload.
Interestingly I ran into a similar scenario today. A client with an SG-2440 and pfSense 2.4.5 upgraded cable from 75/15 to 300/30. Shaping had been configured and working fine when I started. With shaping configured and the numbers adjusted upwards, I couldn't get above 90-100 download after raising the bandwidth. I tried deleting shaping and recreating it a couple of times.
With shaping off, testing could get up to 350 down but the CPU was maxing out (it also had Suricata). With it on, downloading was around 100 Mbps but only 40% CPU.