Re: Utility to limit client access to DHCP Server

Christopher Davis <chr+@andrew.cmu.edu> Sat, 09 March 1996 06:05 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06073; 9 Mar 96 1:05 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06069; 9 Mar 96 1:05 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa01391; 9 Mar 96 1:05 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu; (5.65v3.0/1.1.8.2/29Aug94-0956AM) id AA27855; Sat, 9 Mar 1996 00:58:10 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4) id AA09254; Sat, 9 Mar 1996 00:48:41 -0500
Received: from PO8.ANDREW.CMU.EDU by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA26731; Sat, 9 Mar 1996 00:48:40 -0500
Received: (from postman@localhost) by po8.andrew.cmu.edu (8.7.4/8.7.3) id AAA22620; Sat, 9 Mar 1996 00:48:37 -0500
Received: via switchmail; Sat, 9 Mar 1996 00:48:35 -0500 (EST)
Received: from pcs30.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q000/QF.clEFh6200iWP80eDxI>; Sat, 9 Mar 1996 00:46:46 -0500 (EST)
Received: from pcs30.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/usr11/chr/.Outgoing/QF.klEFh5600iWP4F:Xpc>; Sat, 9 Mar 1996 00:46:45 -0500 (EST)
Received: from mms.4.60.Jan.26.1995.18.43.47.sun4c.411.EzMail.PC.2.0.CUILIB.3.45.SNAP.NOT.LINKED.pcs30.andrew.cmu.edu.sun4c.411 via MS.5.6.pcs30.andrew.cmu.edu.sun4c_411; Sat, 9 Mar 1996 00:46:45 -0500 (EST)
Message-Id: <olEFh5200iWPQF_XgV@andrew.cmu.edu>
Date: Sat, 9 Mar 1996 00:46:45 -0500 (EST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Christopher Davis <chr+@andrew.cmu.edu>
To: dhcp-v4@bucknell.edu, SHAKLES@cliffy.polaroid.com
Subject: Re: Utility to limit client access to DHCP Server
Cc:
In-Reply-To: <01I23P0VPQTQ007TEX@cliffy.polaroid.com>
References: <01I23P0VPQTQ007TEX@cliffy.polaroid.com>

Excerpts from netdev.dhcp-v4: 8-Mar-96 Utility to limit client acc.. by
SHAKLES@cliffy.polaroid. 
> Is there anyone that implements such a server?  Is this such a far out
request?
The dynamic DHCP/BOOTP server that I have written does this on the BOOTP
side. Here at CMU, we wanted give our technichans access to the pool of
dynamic ip's in the dormitories, but not anyone else. This was not one
of my project goals, but added this to the code because of it's
simplicity. 

I'm making a distribution which will compile under SGI, HP and Solaris
in addition to SunOS. At your request, I can add the 6 lines of code
necessary for this to work on the DHCP side. It would be part of a
distribution that I would make availible Monday night.


Chris Davis
Network Development
Carnegie Mellon University