Actions
Bug #8516
openFreeRADIUS requires settings re-saved after pfSense upgrade
Start date:
05/14/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
All
Affected Plus Version:
Affected Architecture:
All
Description
This has happened previously, however I don't remember it occuring with major updates, only _1 or _2.
After the latest pfSense update, FreeRADIUS service will start however clients won't be able authenticate (in my case, wireless clients using WPA2-Enteprise).
Fix is to go to EAP tab and just save the current config after which clients using FreeRADIUS for authentication will be able to authenticate.
Updated by Kris Phillips almost 3 years ago
Is FreeRADIUS communicating on a VIP in your configuration or using the actual interface IP? There is a bug for VIPs needing to be re-saved after upgrades that may be related, if so.
Actions