You may be better posting to the Freeradius maillist but IIRC there are
significant differences between the config files for Freeradius 2 and 3
meaning you have to rewrite the radius config files for version 3 as a
version 2 file will not work.

This is from the freeradius website on upgrading to version 3 from 2...

The configuration for 3.0 is largely compatible with the 2.x.x
configuration. However, it is NOT possible to simply use the 2.x.x
configuration as-is. Instead, it should be re-created.

Hope that helps.

Kind regards,

-----Original Message-----
From: List [] On Behalf Of Sigurd
Sent: 16 February 2018 13:57
Subject: [pfSense] Wireless authentication issues after Freeradius upgrade

We recently purchased a Netgate SG-4860 in order to replace our custom built
desktop hardware.

The desktop hardware was running pfsense 2.3.x and the sg-4860 was running
2.4.0 when delivered. According to Pfsense documentation its possible to
migrate configuration.xml files to newer versions of Pfsense which is what
we did.

After replacing two pieces of hardware most appliances came up correctly as
intended, however after reinstalling Freeradius 3 (over the previously
installed Freeradius 2..x.x) Our radius based wireless SSID's stopped
functioning. With the following error:

"mschap: FAILED: No NT/LM-Password.  Cannot perform authentication"

Tests with the command radtest have worked by authenticating from the
pfsense server itself. However the access points are unable to authenticate.

I have two offices running pfsense 2.3.3 and Freeradius 2 that are currently
working from the same SQL database without any issues.

I have seen several posts with similar issues, but no apparant solution.
Many of these are however authenticating against LDAP and not plain-text SQL
- Among these are:

Notable warnings and errors from the output of "radiusd -X"

[/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item
"FreeRADIUS-Response-Delay" found in filter list for realm "DEFAULT".
[/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item
"FreeRADIUS-Response-Delay-USec" found in filter list for realm "DEFAULT".

 # Loading authorize {...}
Ignoring "sql" (see raddb/mods-available/README.rst) Ignoring "ldap" (see
raddb/mods-available/README.rst) ...

(7) WARNING: Outer and inner identities are the same.  User privacy is

(7)   WARNING: You set Proxy-To-Realm = LOCAL, but the realm does not
exist!  Cancelling invalid proxy request.

(7) mschap: WARNING: No Cleartext-Password configured.  Cannot create
(7) mschap: WARNING: No Cleartext-Password configured.  Cannot create
LM-Password ...

(7) mschap: ERROR: FAILED: No NT/LM-Password.  Cannot perform authentication
(7) mschap: ERROR: MS-CHAP2-Response is incorrect ....

Currently i suspect either an issue when the AP connects to the Freeradius
3 server or an issue in the imported configuration.

Currently using Aerohive for the wireless solution.

Excerp from database:

mysql> select * from radcheck;
| id  | name       | username | attribute          | op | value          |
email                |
|   3 | some name  | username | Cleartext-Password | := | somepassword   |   |
|   6 | some name  | username | Cleartext-Password | := | somepassword   |   |

Issue is crossposted here:

Any assistance in this is appreciated.


Sigurd Kristensen
Systems Administrator


Copenhagen // Artillerivej 86, 2300 Copenhagen, Denmark Aarhus //
Frederiksgade 45, 2. sal, 8000 Aarhus, Denmark London // 174 North Gower
Street, London NW1 2NB, United Kingdom

Mobile: +45 31626876

pfSense mailing list
Support the project with Gold!

This email has been checked for viruses by AVG.

pfSense mailing list
Support the project with Gold!

Reply via email to