You can see it is matching the DEFAULT entry at line 153 (users: Matched DEFAULT at 153) ,
but it does not seem to find this specific username in the users file.
Other recommendation would be to check the "lower_user" option in radiusd.conf.
Freeradius has a few options for matching case sensitivity in usernames (and passwords).
-Rob
At 03:11 PM 11/24/2003 -0800, you wrote:
Rob,
Thanks. I doubled checked. The comma is there. Sorry 'bout that.
I really have no clue what is going on here. The message indicate no password is present in the request, yet in the debug log is it shown. Here is a snippit of the log:
Listening on IP address *, ports 1812/udp and 1813/udp, with proxy on 1814/udp. Ready to process requests. rad_recv: Access-Request packet from host XX.XXX.XXX.XXX:33631, id=139, length=65 User-Name = "00022d-8152d8" User-Password = "blbb" NAS-IP-Address = 192.168.0.200 NAS-Port = 0 modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "eap" returns noop for request 0 rlm_realm: No '@' in User-Name = "00022d-8152d8", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched DEFAULT at 153 modcall[authorize]: module "files" returns ok for request 0 modcall[authorize]: module "mschap" returns noop for request 0 modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type Local auth: type Local auth: No password configured for the user auth: Failed to validate the user.
Any ideas??????
Bill
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
