On Jul 18, 2018, at 2:12 PM, Elias Pereira <empbilly@gmail.com> wrote:
At first everything is ok with the settings. I made internal tests with radtest and the authentication of a domain user is done correctly. I also tested with pfsense's captiveportal and it worked correctly.
We have a wifi controller from the motorola and created a ssid and set the AAA profile as it showed in the extreme support itself.
After trying to connect via mobile with android, the following error occurs:
Read http://wiki.freeradius.org/list-help. We want to see "radiusd -X". Not "radiusd -Xxxxxxxxx"
Wed Jul 18 14:44:25 2018 : Debug: (71) eap_peap: [eaptls process] = ok Wed Jul 18 14:44:25 2018 : Debug: (71) eap_peap: Session established. Decoding tunneled attributes Wed Jul 18 14:44:25 2018 : Debug: (71) eap_peap: PEAP state send tlv success Wed Jul 18 14:44:25 2018 : Debug: (71) eap_peap: Received EAP-TLV response Wed Jul 18 14:44:25 2018 : Debug: (71) eap_peap: Client rejected our response. The password is probably incorrect
That message should be clear.
*Wed Jul 18 14:44:25 2018 : ERROR: (71) eap_peap: We sent a success, but the client did not agree* *Wed Jul 18 14:44:25 2018 : ERROR: (71) eap: Failed continuing EAP PEAP (25) session. EAP sub-module failed*
OK... so you're ignoring the one useful message, and worrying about two *subsequent* messages?
Has anyone ever had this problem?
Yes. When the password is incorrect. If you want to get it working, there is a step-by-step guide on my web site: http://deployingradius.com Alan DeKok.