From owner-freebsd-net Wed Feb 24 23:40:35 1999 Delivered-To: freebsd-net@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E0CB14BD8 for ; Wed, 24 Feb 1999 23:40:33 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id CAA26529; Thu, 25 Feb 1999 02:40:15 -0500 (EST) Date: Thu, 25 Feb 1999 02:40:13 -0500 (EST) From: To: Brian Cully Cc: GVB , freebsd-net@FreeBSD.ORG Subject: Re: RADIUS Solutions In-Reply-To: <19990223192031.C50175@kublai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 23 Feb 1999, Brian Cully wrote: > daemon to query directly against our provisioning system if the > user wasn't in the password file or if his password had been > invalidated. Hacked... your radiusd? '...provisioning system'? Is this to say that you, perhaps, have multiple systems, but they all end up being useless if the one, centralized provisioning system is down? I'm probably just misunderstanding... I'm wanting to setup round-robin radius servers myself (just running one now with a 'standby' that has to be administratively enabled *ack*). I want to ensure that when one box dies, the other gets hit without any intervention on my part. That means it will need it's own copy of the password database... something that NIS seems quite suited to handle... although I'm always open to other alternatives. -- Mike Hoskins Systems/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com "In a world where an admin is rendered useless when the ball in his mouse has been taken out, its good to know that I know UNIX." -- toaster.sun4c.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message