From owner-freebsd-hackers Fri Feb 12 18:34:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13978 for freebsd-hackers-outgoing; Fri, 12 Feb 1999 18:34:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13914 for ; Fri, 12 Feb 1999 18:34:01 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.2/8.9.1) with ESMTP id VAA59322; Fri, 12 Feb 1999 21:32:37 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199902130232.VAA59322@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: brian@Awfulhak.org (Brian Somers), phoenix@calldei.com, netmonger@genesis.ispace.com, freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: ppp server side startup commands References: <199902130215.TAA27651@usr05.primenet.com> In-reply-to: Your message of "Sat, 13 Feb 1999 02:15:35 GMT." <199902130215.TAA27651@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Feb 1999 21:32:37 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > To solve the problem, though: > > > > > > http://www.ietf.org/internet-drafts/draft-ietf-dhc-agent-options-05.txt > > > > > > The PPP server should obtain IP addresses via DHCP. > > > > Sounds a bit messy - does ppp have to manage the lease information (I > > haven't read the doc above yet) ? > > > > It's far easier & more manageable to ask ppp to assign a dynamic IP > > or point it at a radius server. > > The IETF DHC working group would prefer that all software that > obtains IP addresses from a pool use DHCP to do so. > > That includes RADIUS servers. This is just nonsense. Both DHCP and PPP IPCP are used to communicate addresses to end users; each has a particular application where it's most suited. RADIUS servers supply service information to a NAS box. In many cases, the RADIUS response from the server might return a static address (and associated route), or perhaps a token which causes an IP address to get allocated out of a pool. DHCP does not have rich enough semantics to be used as a database query mechanism for a RADIUS server to use. DHCP is for use by the end-system to discover configuration information and not as some sort of generalized query mechanism. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message