Regression #13670
closed
AES-NI support is built into the kernel on snapshots instead of being a module
Added by johnny stecchino over 1 year ago.
Updated over 1 year ago.
Plus Target Version:
23.01
Release Notes:
Force Exclusion
Affected Architecture:
amd64
Description
AES-NI is activated in Advanced/Miscellaneous but dashboard system status shows AES-NI present but inactive
ps this machine also has quick assist
Files
- Tracker changed from Bug to Regression
- Project changed from pfSense Plus to pfSense
- Subject changed from AES-NI crypto module shows as inactive when it is in fact present and active to AES-NI support is built into the kernel on snapshots instead of being a module
- Category changed from Cryptographic Modules to Dashboard
- Status changed from New to Feedback
- Assignee set to Kristof Provost
- Target version set to 2.7.0
- Affected Plus Version deleted (
23.01)
- Plus Target Version set to 23.01
- Release Notes changed from Default to Force Exclusion
on 23.01.a.20221118.0600 if I switch from QAT to AES-NI in the System>Advanced>Miscellaneous, save/apply, then check the dashboard it shows Yes(Active) for both QAT and AES-NI (AES-NI is actually selected).
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
That is normal. Changing the configuration does not unload the other modules since that could cause running processes using those modules to fail in unpredictable ways (and the modules may be busy and not unload at all).
Reboot after switching and it reflects the proper state when it comes back up.
This appears to be working as expected for me, I just tried it switching both ways and it had the correct output after rebooting each time.
- Copied to Regression #13779: SafeXcel support is built into the aarch64 kernel on snapshots instead of being a module added
- Copied to deleted (Regression #13779: SafeXcel support is built into the aarch64 kernel on snapshots instead of being a module)
Also available in: Atom
PDF
Updated by 
Updated by 
