CXL Driver does not support ALTQ
-
Hi there,
If anyone could help with this issue I'd greatly appreciate it!
We just replaced our NIC with a Chelsio T520-CR Dual Port 10GB NIC in our Netgate 7100-1U (Running 22.05). According to the documentation that I've found (linked at bottom of post) the CXL driver should support ALTQ traffic shaping, however we are getting the following errors:
There were error(s) loading the rules: pfctl: "cxl0:" driver does not support altq - The line in question reads [0]:
There were error(s) loading the rules: pfctl: pfctl_rules - The line in question reads [0]:
So far I've tried reassigning all interfaces/VLANs as well as adding the following lines to loader.conf, per cxgbe(4) freebsd documentation:
t4fw_cfg_load="YES"
t5fw_cfg_load="YES"
t6fw_cfg_load="YES"
if_cxgbe_load="YES"Neither has seemed to do the trick. If anyone has any ideas please let me know!
-
Mmm, cxl is certainly listed as altq capable:
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/interfaces.inc#L6812You are running 22.05?
Steve
-
@stephenw10 Yessir, 22.05.
-
Hmm, yeah it seems like something in the driver itself that pfctl objects to. Looking....
-
@stephenw10 Just a heads up, I've restored to Factory Defaults and started configuring and I'm no longer getting the error. Thanks for looking into it though! I'll follow up if the error pops up again.
-
Huh, that's interesting. Any idea what else you might have had configured there that made it present differently?
-
@stephenw10 We were using different NICs (Intel X710-BM2) that were shipped with the boxes in a High Availability setup, but realized after configuring that they don't support ALTQ (we were already using VLANs and wanted all traffic to be able to be shaped as a single pipe/shared bandwidth). So that's why we ordered and installed the Chelsio NICs. I switched over the interfaces but was getting that error until I restored to factory defaults. Not sure what could have been causing it. We'll see if any issues pop up again!
-
@stephenw10 I'm not sure when this started, but I've tried configuring traffic shaping again and it is giving me the same filter reload error.
-
I assume that this issue could be related to the following:
https://redmine.pfsense.org/issues/12499
I'm going to be trying to set up some time next week to see whether traffic is being pushed through queues properly or not, despite the error. I'll update with any results. If there's something else that you think I could do to help with troubleshooting please let me know!
-
The cc driver is not cxl it's a different nexus generation. I forget which is which.
Which error is it giving you? When yon run filter reload?
Steve
-
@stephenw10 I'm getting the following errors:
There were error(s) loading the rules: pfctl: "cxl0:" driver does not support altq - The line in question reads [0]:
There were error(s) loading the rules: pfctl: pfctl_rules - The line in question reads [0]:
-
I assume that persists across a reboot? That second error could be a known issue that isn't persistent.
Steve
-
The "cxl0: driver does not support altq" error starts immediately upon enabling the shaper on the interface and persists through reboots.
The "pfctl_rules" error does not start until the filter is reloaded after enabling the shaper. It also persists through reboots, and does not stop until both the shaper is disabled and the system is rebooted.
Edited to correct when pfctl_rules error starts.
-
Hmm, let me see if I can replicate this...
-
@stephenw10 If it helps I'm happy to send my config over to you.
-
It's more a matter of getting some hardware setup to test against. I think I have something now.
-
Ok, I replicated that:
There were error(s) loading the rules: pfctl: cxl0: driver does not support altq - The line in question reads [0]: @ 2022-11-03 18:47:01Investigating...
-
@stephenw10 Hi there, I just wanted to check in and see if you had any updates, or anything you wanted me to try out on my setup that could help narrow things down? I haven't really gotten to delve much further into the issue myself, so unfortunately I don't have any new discoveries just yet.
-
Yeah, it appears the driver itself does not support altq and has not for some years.
There is a lot on conflicting info in threads and redmine tickets here to suggest that it has done. However the driver code shows is was removed and could not have worked.We are looking at options but adding it will be non-trivial.
Steve
-
@stephenw10 Okay, thank you for that info and for looking into this for me! Could you point me in the right direction on where I should check in occasionally to keep an eye on the status of this?
