From owner-freebsd-isp Fri Feb 6 19:44:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28903 for freebsd-isp-outgoing; Fri, 6 Feb 1998 19:44:31 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28878 for ; Fri, 6 Feb 1998 19:44:21 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id OAA17458; Sat, 7 Feb 1998 14:43:54 +1100 (EST) Date: Sat, 7 Feb 1998 14:43:54 +1100 (EST) From: "Daniel O'Callaghan" To: David Babler cc: freebsd-isp@FreeBSD.ORG Subject: Re: User PPP/PAP & IPs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-isp" > 1. allow only specific PPP/PAP logins from specific users on > specific lines and deny all others, even if they have valid > passwords. (e.g. dedicated-line customers) You'll have to write an ip-up script to disconnect unauthorised attempts. > 2. allow PPP/PAP dialups on other ports and have them recognized > as either "normal" accounts, which get a dynamic IP (or a fixed IP > for specific ports) or "static IP" accounts and issue them a > user-specific static IP. It's acceptable for the static IP users' > passwords to be in ppp.secret but I'd prefer the "normal" > users' passwords to come from passwd from an administrative > standpoint. Add the following to /etc/ppp/pap-secrets me * "" :203.1.2.4 friend * "" :203.1.2.5 * * "" The last line allows the IP address specified in options.ttyXn to be used, the first two override options.ttyXn for the remote IP address. Danny