Date: Tue, 21 Feb 2012 06:58:55 -0600 From: "Paul A. Procacci" <pprocacci@datapipe.com> To: saeedeh motlagh <saeedeh.motlagh@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: must define username in radius client??? Message-ID: <20120221125855.GK12291@nat.myhome> In-Reply-To: <CAN%2BS=WBRzmNm5JvGQ1qEupGTafz8ODCqWbjwd-tuYsoOPc%2BT8A@mail.gmail.com> References: <CAN%2BS=WBRzmNm5JvGQ1qEupGTafz8ODCqWbjwd-tuYsoOPc%2BT8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Assuming ssh (you didn't specify), you only need to setup the shared secret= between machines. The rest is handled by pam/login as normal (ala "auth s= ufficient pam_radius.so") cat /etc/radius.conf #################################### auth 10.5.21.4:1645 "SuperSkret" 3 2 auth 10.5.21.5:1645 "SuperSkret" 3 2 ~Paul On Tue, Feb 21, 2012 at 11:24:03AM +0330, saeedeh motlagh wrote: > hello guys, > i wanna have authentication via radius server. in my local network, > one system is radius server and the others are clients. the server is > running well. when a client login, it sends an access-request to the > server. if the user name and password are defined in the server, the > server sends back the access-accept to client. if the user name is > defined in the client, the login is successful but if this user name > is not defined in the client, the login failed and say "login > incorrect" although the client receives access-accept from the server. > i wanna know if there is any way to have authentication successfully > without defining any user name in the client system? > yours, > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" ________________________________ This message may contain confidential or privileged information. If you are= not the intended recipient, please advise us immediately and delete this m= essage. See http://www.datapipe.com/legal/email_disclaimer/ for further inf= ormation on confidentiality and the risks of non-secure electronic communic= ation. If you cannot access these links, please notify us by reply message = and we will send the contents to you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120221125855.GK12291>