Calling eap_md5 to process EAP data in inner-tunnel

Alan DeKok aland at deployingradius.com
Wed Oct 8 13:52:38 CEST 2014


Oleksandr Yermolenko wrote:
> sorry, really full radiusd -X
...

> (6)  eap_ttls : Sending tunneled request
> (6)  server inner-tunnel {
> (6)    Request:
>     EAP-Message = 0x020100160410600a49ae5d212341b6be08f34c3de38e
>     User-Name = 'stu at sumix.com'
>     State = 0xd1c37efdd1c27a33ce26defdbde2d5d4

  That seems clear.

> (6)  # Executing section authorize from file
> /etc/raddb/sites-enabled/inner-tunnel
> (6)    authorize {
> (6)   eap : Peer sent code Response (2) ID 1 length 22
> (6)   eap : No EAP Start, assuming it's an on-going EAP conversation
> (6)    [eap] = updated
> (6)    [files] = noop

  And the user isn't found.

> (6)   eap : Calling eap_md5 to process EAP data
> (6)   eap_md5 : Cleartext-Password is required for EAP-MD5 authentication

  Which is why this fails.

  Alan DeKok.


More information about the Freeradius-Users mailing list