Bug #3226

Captive Portal Radius Error

Added by Nicholas Schirmer about 7 years ago. Updated over 6 years ago.

Captive Portal
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


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/ on line 105

Did something get lost in the upgrade?

Associated revisions

Revision 2d72659a (diff)
Added by Renato Botelho almost 7 years ago

Set default value to radius_protocol during upgrade, it should fix #3226

Revision a518b337 (diff)
Added by Renato Botelho almost 7 years ago

Set default value to radius_protocol during upgrade, it should fix #3226


#1 Updated by Renato Botelho about 7 years ago

  • Priority changed from High to Normal

Seems that parameter radius protocol is empty. Could you please confirm it?

#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

Client Machine:
Security ID: NULL SID
Account Name: -
Fully Qualified Account Name: -
OS-Version: -
Called Station Identifier:
Calling Station Identifier: 00:24:2c:7a:fc:7d

NAS IPv4 Address:
NAS IPv6 Address: -
NAS Identifier:
NAS Port-Type: Ethernet
NAS Port: 5270

RADIUS Client:
Client Friendly Name: Firewall
Client IP Address:

Authentication Details:
Proxy Policy Name: Use Windows authentication for all users
Network Policy Name: Secure Wireless Connections
Authentication Provider: Windows
Authentication Server:
Authentication Type: MS-CHAPv1
EAP Type: -
Account Session Identifier: -

Quarantine Information:
Result: Full Access
Extended-Result: -
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,, 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 ( but PFSense isn't receiving the correct response.

#3 Updated by Renato Botelho almost 7 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#5 Updated by Renato Botelho over 6 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF