<![CDATA[Any chance to cherrypick this fix for wpa-supplicant?]]>After upgrading to the 2.5.X series, using wpa-supplicant causes pfSense to run at 100% CPU on one core. This is being experienced by me and many others that use the wpa-supplicant to directly attach pfSense to an AT&T Fiber ONT, as well as other use cases that involve wifi radios.

Killing wpa-supplicant after startup and restarting it fixes the problem. I believe the underlying problem is referenced in this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252844 and the fix should work in pfSense as well.

Can we get this put on the list for the next . release? A lot of us are burning excess power by running with this bug in place.

Thanks!

]]>https://forum.netgate.com/topic/163282/any-chance-to-cherrypick-this-fix-for-wpa-supplicantRSS for NodeMon, 09 Mar 2026 05:27:44 GMTMon, 26 Apr 2021 04:21:24 GMT60<![CDATA[Reply to Any chance to cherrypick this fix for wpa-supplicant? on Mon, 26 Apr 2021 05:51:49 GMT]]>There does seem to be some testing being done.
https://github.com/MonkWho/pfatt/issues/41#issuecomment-826134521

Redmine: https://redmine.pfsense.org/issues/11453
Positive/Negative responses to testing is encouraged.

Request mod bump this over to dev category:
https://forum.netgate.com/category/28/development

]]>https://forum.netgate.com/post/979824https://forum.netgate.com/post/979824Mon, 26 Apr 2021 05:51:49 GMT