Bug #6830
closed
- Category set to Traffic Shaper (ALTQ)
- Target version changed from 2.3.2-p1 to 2.4.0
Can't target 2.3.2_1 as it's already been built.
There was a deliberate reason this was left out but I'll have to dig up the details tomorrow. Most likely reason was that it made no sense to allow. The performance hit you'd take for doing ALTQ on a 10G interface would never be worth it. You wouldn't gain much if anything from shaping at those speeds.
Jim Pingle wrote:
Can't target 2.3.2_1 as it's already been built.
There was a deliberate reason this was left out but I'll have to dig up the details tomorrow. Most likely reason was that it made no sense to allow. The performance hit you'd take for doing ALTQ on a 10G interface would never be worth it. You wouldn't gain much if anything from shaping at those speeds.
Well, ISP is limiting our network connectivity to 2GBps. With notes on 10gbps cards, I would assume that trying to traffic shape that quantity of traffic would be a bottleneck on the nic cards and/or cpu.
TL;DR:
I'm trying to traffic shape less than 3gbps on a 10gbps card.
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
It's in the list now for snapshots.
- Assignee set to Renato Botelho
- Target version changed from 2.4.0 to 2.3.3
- Affected Version set to All
This bug does not appear to be fixed in 2.3.3-p1.
When I try to use altq with a Chelsio T520-SO-CR I still get an error about cxl not supported by altq. I believe my error coming from the actual firewall and not the web ui.
Please see this thread for more details:
https://forum.pfsense.org/index.php?topic=129476.0
Using Chelsio T4 on;
2.4.0-BETA (amd64)
built on Fri May 26 19:15:04 CDT 2017
FreeBSD 11.0-RELEASE-p10
This is not fixed.
"This firewall does not have any interfaces assigned that are capable of using ALTQ traffic shaping."
Also available in: Atom
PDF