I've seen it and there it is said that we can use crypt passwords but inmy case i have an access-reject:
rad_recv: Access-Request packet from host 127.0.0.1 port 58647, id=108, length=5 7
User-Name = "steve"
User-Password = "xxxxx"
NAS-IP-Address = 172.30.10.71
NAS-Port = 1812
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
[suffix] No
'@' in User-Name = "steve", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[files] users: Matched entry steve at line 76
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
++[pap] returns updated
Found Auth-Type = PAP
+- entering group PAP {...}
[pap] login attempt with password "testing"
[pap] Using CRYPT encryption.
[pap] Passwords don't match
++[pap] returns reject
Failed to authenticate the user.
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject] expand: %{User-Name} -> steve
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 0 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 0
Sending Access-Reject of id 108 to 127.0.0.1 port 58647
Waking up in 4.9 seconds.
Cleaning up request 0 ID 108 with timestamp +20