Hi, I wanted to authenticate username "testing" with password "password". First I used the "radtest" utility and I've got radtest testing password 127.0.0.1 0 testing123 Sending Access-Request of id 132 to 127.0.0.1 port 1812 User-Name = "testing" User-Password = "password" NAS-IP-Address = 127.0.0.1 NAS-Port = 0 Message-Authenticator = 0x00000000000000000000000000000000 rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=132, length=20 Then try to use "radlogin" utility to do the authentication (I uncommented the line in file /usr/local/etc/radiusclient/servers to make the shared secret to be testing 123), I got radlogin ($Id: radlogin.c,v 1.9 2008/01/09 07:04:18 sobomax Exp $) ----------------------------------------------------- Linux 2.6.9-1.667smp (softdev2.local.4rf.com) (port 2) ----------------------------------------------------- login: testing Password: RADIUS: /dev/pts/2local: Authentication failure Note during the above testing, the freeradius server did not receive any request. It looks like I missed some configure in the client side as "radtest" worked. Could somebody help me what I have missed. Cheers, -----Original Message----- From: freeradius-users-bounces+frank.wei=4rf.com@lists.freeradius.org [mailto:freeradius-users-bounces+frank.wei=4rf.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Monday, 22 September 2014 2:15 p.m. To: FreeRadius users mailing list Subject: Re: Beginner need help Frank Wei wrote:
The only useful information on the freeradius client is
radiusclient [-f config_file] [-p nas_port] [-s | [-a] a1=v1 [a2=v2[...[aN=vN]...]]]
Not how to use above to test the client. How can I create the "config_file" ?
See etc/radiusclient.conf in the "tar" file. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).