Captive Portal Radius Error
Freshly auto-upgraded from 2.0.3 and on my first attempt to login to the captive portal, I received the following error:
Fatal error: Class 'Auth_RADIUS_' not found in /usr/local/captiveportal/radius_authentication.inc on line 105
Did something get lost in the upgrade?
#2 Updated by Nicholas Schirmer about 7 years ago
It appears that it had been reset - instead of MSCHAPV1 it was listed as PAP. Saving it back to MSCHAPV1 and the error went away.
I am now having an issue where I am still being told "Invalid Login. Please try again."
Checking the log of the Windows Radius Server, it says that it granted access to the username.
Network Policy Server granted full access to a user because the host met the defined health policy.
Security ID: TIS\nschirmer
Account Name: nschirmer
Account Domain: TIS
Fully Qualified Account Name: TIS\nschirmer
Security ID: NULL SID
Account Name: -
Fully Qualified Account Name: -
Called Station Identifier: 192.168.1.1
Calling Station Identifier: 00:24:2c:7a:fc:7d
NAS IPv4 Address: 192.168.1.1
NAS IPv6 Address: -
NAS Identifier: pfsense.campus.tisweb.net
NAS Port-Type: Ethernet
NAS Port: 5270
Client Friendly Name: Firewall
Client IP Address: 192.168.1.1
Proxy Policy Name: Use Windows authentication for all users
Network Policy Name: Secure Wireless Connections
Authentication Provider: Windows
Authentication Server: china.campus.tisweb.net
Authentication Type: MS-CHAPv1
EAP Type: -
Account Session Identifier: -
Result: Full Access
Session Identifier: -
Help URL: -
System Health Validator Result(s): -
But in PFSense, I receive the following error in portalauth.log:
Sep 26 08:51:31 pfsense logportalauth6150: ERROR: nschirmer, 00:24:2c:7a:fc:7d, 192.168.1.100, Error sending request: No valid RADIUS responses received
So it appears that now I can connect to China (the radius server) to authenticate me (nschirmer) on PFSense (192.168.1.1) but PFSense isn't receiving the correct response.