On 08/09/2020 09:30, Shaun Hoofe wrote:
(6) eap: EAP session adding &reply:State = 0xcef5e17acefdfb91 (6) [eap] = handled (6) } # authenticate = handled (6) } # server inner-tunnel (6) Virtual server sending reply (6) EAP-Message = 0x0108002a1a0108002510b32b3c4603cdfbd861dec80ae9c95905667265657261646975732d332e302e38
FreeRADIUS requests MS-CHAPv2 (EAP type 0x1A).
(7) eap: Peer sent method PEAP (25) (7) eap: EAP PEAP (25) (7) eap: Calling eap_peap to process EAP data (7) eap_peap: processing EAP-TLS (7) eap_peap: eaptls_verify returned 7 (7) eap_peap: Done initial handshake (7) eap_peap: eaptls_process returned 7 (7) eap_peap: FR_TLS_OK (7) eap_peap: Session established. Decoding tunneled attributes (7) eap_peap: PEAP state phase2 (7) eap_peap: EAP type NAK (3) (7) eap_peap: Got tunneled request (7) eap_peap: EAP-Message = 0x020800060306 (7) eap_peap: Setting User-Name to00703070@harper-adams.ac.uk (7) eap_peap: Sending tunneled request to inner-tunnel (7) eap_peap: EAP-Message = 0x020800060306
...
(7) eap: Peer sent method NAK (3) (7) eap: Found mutually acceptable type GTC (6) (7) eap: Calling eap_gtc to process EAP data
Device comes back, inside the PEAP tunnel NAKs the request (0x03) and asks instead for GTC (0x06). It's not FreeRADIUS. -- Matthew