Correction #12659
closed
Correct inaccuracies in configuring Flow Control for ``ix`` and ``ixl`` interfaces
100%
Description
Page: https://docs.netgate.com/pfsense/en/latest/hardware/tune.html
Feedback:
The entry for Flow Control for ixgbe(4) (aka ix).
Above the entry it says to put the config in system tunables.
When I do that it works for the current boot, but on the reboot it isn't active until I do a change->save in system tunables.
I checked the original readme for the driver from Microsoft (https://www.intel.com/content/www/us/en/download/14303/intel-network-adapters-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html)
There it gave options for putting in /boot/loader.conf.
hw.ix.flow_control=0
I put that into /boot/loader.conf.local, and then the setting survived reboots (I could also remove the system tunables, the /boot/loader.conf.local row was enough).
Updated by Marcos M over 2 years ago
Looks like this applies to ixl as well: https://www.intel.com/content/www/us/en/download/18331/intel-network-adapter-driver-for-intel-ethernet-controller-700-series-under-freebsd.html
hw.ixl.flow_control=0 should be set in /boot/loader.conf.local.
Perhaps there's an issue with the system tunables for NICs being set too late/early in the boot process?
Updated by Jim Pingle almost 2 years ago
- Tracker changed from Todo to Correction
- Subject changed from Feedback on Hardware — Hardware Tuning and Troubleshooting - Flow Control for ix to Correct inaccuracies in configuring Flow Control for ``ix`` and ``ixl`` interfaces
Updated by Chris W over 1 year ago
Should the "ixgbe(4) (aka ix)" part be removed from under the System Tunables area since it's already present in the section further above which says to put it in /boot/loader.conf.local, or is this an alternate method which should work but need to investigate further?
For what it's worth, I can add a system tunable to disable flow control for igb0 and igb1 on a 5100 and that survives reboots, but not for its ix interfaces.
Updated by Jim Pingle over 1 year ago
Chris W wrote in #note-3:
Should the "ixgbe(4) (aka ix)" part be removed from under the System Tunables area since it's already present in the section further above which says to put it in /boot/loader.conf.local, or is this an alternate method which should work but need to investigate further?
For what it's worth, I can add a system tunable to disable flow control for igb0 and igb1 on a 5100 and that survives reboots, but not for its ix interfaces.
The tunable method for ix may be outdated/for old versions. If it doesn't work on a current release it should be removed.
Updated by Chris W over 1 year ago
- % Done changed from 0 to 90
- From what I can see on a 5100 with both 22.05 and 22.01:
- Default settings are: dev.ix.#.fc=0 and hw.ix.flow_control=3
- Setting dev.ix.0.fc to 2 (since setting it to 0 wouldn't be helpful here) as a system tunable immediately shows with sysctl -a | grep ix.0.fc. Can also be set from the command line but neither method survives reboots.
- Setting sysctl hw.ix.flow_control=0 from the command line (both GUI and CLI) returns:
sysctl: oid 'hw.ix.flow_control' is a read only tunable
sysctl: Tunable values are set in /boot/loader.conf
- Setting inline hw.ix.flow_control=0 in /boot/loader.conf.local (with or without double quotes around the value) works and survives reboots:
[22.01-RELEASE][root@pfSense.home.arpa]/root: sysctl -a | grep flow_ hw.ixl.flow_control: -1 hw.ix.flow_control: 0
Merge request to remove the system tunable method for ix:
https://gitlab.netgate.com/docs/pfSense-docs/-/merge_requests/48
Updated by Jim Pingle over 1 year ago
- Status changed from New to Resolved
- % Done changed from 90 to 100
Merged and deployed.