Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Upgrade 2.4 killed my wpa2-eap with ntlm passwords

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 2 Posters 950 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Gerard64
      last edited by

      After upgrading to pfsense 2.4 I was forced to upgrade to Freeradius 3. Now I can't login anymore on my wpa2-eap wifi network from any device (Windows 7, Android 7).

      "Login incorrect (mschap: FAILED: No NT/LM-Password. Cannot perform authentication):"

      Before it worked with ntlm passwords.

      Somebody any idea what the problem is. Else I need to go back to version 2.3 till I figur out what the problem is.

      1 Reply Last reply Reply Quote 0
      • F
        Finger79
        last edited by

        Try rebooting manually.  I had WPA2-EAP issues after an upgrade, and rebooting manually resolved it, as silly as it sounds.

        1 Reply Last reply Reply Quote 0
        • G
          Gerard64
          last edited by

          After upgrading to 2.4 I had a mounting problem (error 19 see: https://forum.pfsense.org/index.php?topic=137929.0). To fix this I had to reboot several times. Now after several hours sleep I rebooted again but WPA2-EAP is still nog working. I use Freeradius also for captive portal and openvpn both work just wpa-eap is not working. I restarted the accesspoints but it keep giving:

          Oct 13 13:23:27 radiusd 48737 (38) Login incorrect (mschap: FAILED: No NT/LM-Password. Cannot perform authentication): [Username] (from client AP2 port 0 via TLS tunnel)
          Oct 13 13:23:20 radiusd 48737 (30) Login incorrect (eap_peap: The users session was previously rejected: returning reject (again.)): [anonymous] (from client AP3 port 0 cli F0-D7-AA-xx-xx-xx)

          1 Reply Last reply Reply Quote 0
          • G
            Gerard64
            last edited by

            Today I reinstalled 2.4 used a backup config. Problem still there. Then I reinstalled 2.3 again with the same backup config and everything is working again. So for me no 2.4 yet.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.