From owner-freebsd-net@FreeBSD.ORG Sun Feb 26 06:25:35 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A1F3106566C for ; Sun, 26 Feb 2012 06:25:35 +0000 (UTC) (envelope-from saeedeh.motlagh@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id AFF2E8FC16 for ; Sun, 26 Feb 2012 06:25:34 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so347841bkc.13 for ; Sat, 25 Feb 2012 22:25:33 -0800 (PST) Received-SPF: pass (google.com: domain of saeedeh.motlagh@gmail.com designates 10.204.156.219 as permitted sender) client-ip=10.204.156.219; Authentication-Results: mr.google.com; spf=pass (google.com: domain of saeedeh.motlagh@gmail.com designates 10.204.156.219 as permitted sender) smtp.mail=saeedeh.motlagh@gmail.com; dkim=pass header.i=saeedeh.motlagh@gmail.com Received: from mr.google.com ([10.204.156.219]) by 10.204.156.219 with SMTP id y27mr4094696bkw.110.1330237533726 (num_hops = 1); Sat, 25 Feb 2012 22:25:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wL+lnVsxeKZ3zjyOWpFYDKLOvvdHRGrIGYYbflhtPgw=; b=x6yOZU1rGjlhU6S2vt8RpSOtTkeG+9Z3PQQ2/09ZBKZmULdzCtPkYzP6G8HI5o01Sf 4pihsG6WG/Oz9DKzqw1IK0Gl2UA01jPpNHvolvE74x5xa0Zg0dIpbFrQkyPSxzuEzq/6 1VklponG8vlXn9/QVjUryeDcTub89EHUfMKTY= MIME-Version: 1.0 Received: by 10.204.156.219 with SMTP id y27mr3330613bkw.110.1330237533519; Sat, 25 Feb 2012 22:25:33 -0800 (PST) Received: by 10.204.201.67 with HTTP; Sat, 25 Feb 2012 22:25:33 -0800 (PST) In-Reply-To: <20120221125855.GK12291@nat.myhome> References: <20120221125855.GK12291@nat.myhome> Date: Sun, 26 Feb 2012 09:55:33 +0330 Message-ID: From: saeedeh motlagh To: "Paul A. Procacci" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net Subject: Re: must define username in radius client??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2012 06:25:35 -0000 thanks paul i do that, the client sends request and the server accepts it and send response. the client receives this access accept response but login failed. if i define the username without the password in client system, login will be successful. do you know what's the problem? please tell me if you know what should i do now thank you very much yours motlagh On 2/21/12, Paul A. Procacci wrote: > 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 > sufficient 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 > message. See http://www.datapipe.com/legal/email_disclaimer/ for further > information on confidentiality and the risks of non-secure electronic > communication. If you cannot access these links, please notify us by reply > message and we will send the contents to you. >