As you guess, now I am stucked in EAP problem as described in http://deployingradius.com/documents/configuration/eap-problems.html Problem: A lot of text scrolls by, the server sends an Access-Challenge, and then prints out a message saying Cleaning up request .... After that, nothing more happens. I have followed the instructed solution on the web, but I still have the same problem. What might be the trouble? this is my log output: rad_recv: Access-Request packet from host 10.0.0.2 port 1027, id=169, length=189 User-Name = "PIDEL-3C5B30E9C\\Administrator" NAS-IP-Address = 10.0.0.2 NAS-Port = 0 Called-Station-Id = "00-1E-E5-9D-61-85:DEL_LR1" Calling-Station-Id = "00-21-00-0B-68-E3" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x020c00061900 State = 0x8e584f678d5456652c4dc94a57520460 Message-Authenticator = 0x7b7251c229539af1b067c6bf5161a3e8 +- entering group authorize ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop rlm_realm: No '@' in User-Name = "PIDEL-3C5B30E9C\Administrator", looking up realm NULL rlm_realm: No such realm "NULL" ++[suffix] returns noop rlm_eap: EAP packet type response id 12 length 6 rlm_eap: Continuing tunnel setup. ++[eap] returns ok rad_check_password: Found Auth-Type EAP auth: type "EAP" +- entering group authenticate rlm_eap: Request found, released from the list rlm_eap: EAP/peap rlm_eap: processing type peap rlm_eap_peap: Authenticate rlm_eap_tls: processing TLS rlm_eap_tls: Received EAP-TLS ACK message rlm_eap_tls: ack handshake fragment handler eaptls_verify returned 1 eaptls_process returned 13 rlm_eap_peap: EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 169 to 10.0.0.2 port 1027 EAP-Message = 0x010d00061900 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x8e584f678a5556652c4dc94a57520460 Finished request 9. Going to the next request Waking up in 4.9 seconds. Cleaning up request 5 ID 165 with timestamp +305 Cleaning up request 6 ID 166 with timestamp +305 Cleaning up request 7 ID 167 with timestamp +305 Cleaning up request 8 ID 168 with timestamp +305 Cleaning up request 9 ID 169 with timestamp +305 Ready to process requests. thanks. On Fri, Aug 8, 2008 at 4:02 PM, Lech Karol Pawłaszek <ike@szluug.org> wrote:
Ramot Lubis wrote:
Thanks Alan, it was my mistake. I have fixed the openssl trouble. Now PEAP is running. But I still have problem with authentication.
I put the log here. Please, tell me what my next mistake is.
[...]
Sending Access-Challenge of id 76 to 10.0.0.2 port 1027 EAP-Message = 0x010d00061900 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x61fcdc3965f1c5fd5ac44742bec48a4e Finished request 9.
Lucky guess...
http://deployingradius.com/documents/configuration/eap-problems.html
:-) kind regards, -- Lech Karol Pawłaszek <ike> "You will never see me fall from grace" [KoRn] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html