FreeRadius 2.1.1 with PEAP- EAP-MD5

[tnt at kalik.net]

server (null) {
  PEAP: Setting User-Name to queenie
Sending tunneled request
        EAP-Message = 0x020900160410ef6cb6c0397ac7d4c05bf94e3f25b91f
        FreeRADIUS-Proxied-To = 127.0.0.1
        User-Name = "queenie"
        State = 0xcec54cd4cfcc481d16e979e447d690e2
server inner-tunnel {
+- entering group authorize {...}
++[chap] returns noop
++[mschap] returns noop
++[unix] returns notfound
[suffix] No '@' in User-Name = "queenie", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
++[control] returns noop
[eap] EAP packet type response id 9 length 22
[eap] No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
[files] users: Matched entry queenie at line 91
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
[pap] Found existing Auth-Type, not changing it.
++[pap] returns noop
Found Auth-Type = EAP
+- entering group authenticate {...}
[eap] Request found, released from the list
[eap] EAP/md5
[eap] processing type md5
[eap] Freeing handler
++[eap] returns reject
Failed to authenticate the user.

That is when things go wrong. It goes to process md5 and returns reject.
There is no moaning about wrong password or anything else.

Ivan Kalik
Kalik Informatika ISP