Hello, why if I have in my clients.conf this configuration: client localhost { secret = testing123 nastype = other shortname = localhost login = test password = test } and I try #radtest test test localhost testing123 say: Sending Access-Request of id 231 to 201.220.197.66 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 255.255.255.255 NAS-Port = 0 Re-sending Access-Request of id 231 to 201.220.197.66 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 255.255.255.255 NAS-Port = 0 rad_recv: Access-Reject packet from host locahost:1812, id=231, length=20 Why is Access-Reject? There is a bug of freeradius? some idea?
"Abel Monzon" <jame@yumuri.mtz.sld.cu> wrote:
Why is Access-Reject? There is a bug of freeradius?
Run the server in debugging mode and it will tell you why it's sending a reject. This is documented in the README, FAQ, INSTALL, and daily on this list. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hello, why if I have in my clients.conf this configuration:
client localhost { secret = testing123 nastype = other shortname = localhost login = test password = test }
and I try #radtest test test localhost testing123
----- Original Message ----- From: "Alan DeKok" <aland@deployingradius.com> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Thursday, October 05, 2006 10:20 PM Subject: Re: freeradius bug?
"Abel Monzon" <jame@yumuri.mtz.sld.cu> wrote:
Why is Access-Reject? There is a bug of freeradius?
Run the server in debugging mode and it will tell you why it's sending a reject.
This is documented in the README, FAQ, INSTALL, and daily on this list.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Información de NOD32, revisión 1.1237 (20050929) __________
Este mensaje ha sido analizado con NOD32 antivirus system http://www.nod32.com
This is the answer of radtest: ........ Module: Instantiated files (files) Module: Loaded radutmp radutmp: filename = "/usr/local/var/log/radius/radutmp" radutmp: username = "%{User-Name}" radutmp: case_sensitive = yes radutmp: check_with_nas = yes radutmp: perm = 384 radutmp: callerid = yes Module: Instantiated radutmp (radutmp) Listening on authentication *:1812 Listening on accounting *:1813 Ready to process requests. rad_recv: Access-Request packet from host 201.220.197.67:32840, id=166, length=50 Service-Type = Framed-User User-Name = "test" User-Password = "test" Processing the authorize section of radiusd.conf 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 "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "test", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 modcall: leaving group authorize (returns ok) for request 0 auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user auth: Failed to validate the user. Login incorrect: [test/test] (from client localhost port 0) Delaying request 0 for 1 seconds Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Sending Access-Reject of id 166 to 201.220.197.67 port 32840 Waking up in 4 seconds... --- Walking the entire request list --- Cleaning up request 0 ID 166 with timestamp 4526856b Nothing to do. Sleeping until we see a request. I not see the problem....
"Abel Monzon" <jame@yumuri.mtz.sld.cu> wrote: ...
auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user
You didn't tell the server what the "known good' password is for the user. See the FAQ for how to configure a test user. There IS documentation for the server. Go read it. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hi,
Hello, why if I have in my clients.conf this configuration:
client localhost { secret = testing123 nastype = other shortname = localhost login = test password = test }
and I try #radtest test test localhost testing123
err, the login and password entries are for backend utilities such as simultaneous usage checking (and other SNMP/telnet tools). for this command to work, you have to add a 'test' user to either your users file or to your SQL database, AD, etc etc look at the users file for an example user entry that you can copy/edit at your will. try changing the users entry to reject, accept and add a reply message etc to see stuff being sent back to your radtest command alan
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Abel Monzon -
Alan DeKok