From owner-freebsd-isp Fri May 30 16:32:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15484 for isp-outgoing; Fri, 30 May 1997 16:32:11 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15476 for ; Fri, 30 May 1997 16:32:06 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA19052; Sat, 31 May 1997 09:31:44 +1000 (EST) Date: Sat, 31 May 1997 09:31:43 +1000 (EST) From: "Daniel O'Callaghan" To: "Robert P. Ricci" cc: freebsd-isp@FreeBSD.ORG Subject: Re: Authenticating dial-ins In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 May 1997, Robert P. Ricci wrote: > We've got two FreeBSD machines, and would like to use one as a terminal > server and the other as mail/web/ftp sever (right now, everything's on > the terminal server.) What would be the best way to keep identical > password files on both machines, or use the web server's password file to > authenticate users on the terminal server? The terminal server uses a > cyclades card. Right now, we use mgetty to answer the modems, which then > fires up pppd. We're also able to nfs mount between the two machines. Right now, your best hope is probably NIS. Adam David and I are vaguely working towards getting radius client support into pppd. You could contact and ask him how he did his radius login stuff. I think he replaced login with radlogin. Getting radiusd to read your local password file is not easy, though - it has a separate password/attributes file. /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */