From owner-freebsd-isp Wed May 31 7:51:38 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 7F60B37B6B3 for ; Wed, 31 May 2000 07:51:34 -0700 (PDT) (envelope-from troy@picus.com) Received: from arcadia [209.100.20.198] by durango.picus.com (SMTPD32-5.05) id A69AA20208; Wed, 31 May 2000 10:50:02 -0400 From: "Troy Settle" To: "William Lloyd" Cc: "Corey Ralph" , Subject: RE: Using radius to NT server? Date: Wed, 31 May 2000 10:54:07 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <20000531104253.C12953@galt.slap.net> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** I've not tried it with a NT radius server but the pam_radius ** stuff requires ** that a full user account be setup on the freebsd box. The pam_radius ** module will ignore the password part of the account and verify against ** the other (in your case NT) radius box. ** ** Don't think of it as a replacement for NIS/YP in this case. I really wish it was a complete replacement for NIS/YP and/or the passwd file, but I accept these limitations for now. ** ** You might check the TCP port that radius is using. Different ** radius servers ** seem to use different default ports. I think Livingston changed ** the radius ** default port somewhere along the line a while back. The entry in /etc/radius.conf looks like this: auth 192.168.10.2:1645 secret It's correct according to the docs, and matches up with what 60 or so NAS are using :) Thanks, -Troy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message