Re: DHCP and secondaries

Tim Peiffer <peiffer@nts.umn.edu> Thu, 16 May 1996 04:01 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05887; 16 May 96 0:01 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05883; 16 May 96 0:01 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa01364; 16 May 96 0:01 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA25166; Wed, 15 May 1996 23:57:10 -0400
Date: Wed, 15 May 1996 23:57:10 -0400
Message-Id: <199605160319.AA07981@mome.unet.umn.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Peiffer <peiffer@nts.umn.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP and secondaries
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL21]

I would settle for random.  Right now, I have a need for
coverage (quantity) in excess of what I can currently
deliver.

Tim

> 
> 
> > Does anyone know of a pointer to a DHCP package that
> > supports the use of secondary addresses (i.e, multiple
> > logical subnets on one interface)?
> 
> Do you want to be able to allocate addresses to any of the subnets, or
> just to the new one that you're migrating to?  If the former, how
> should the server choose which net a given host should wind up on, or
> should it just choose one at random?  I'm planning to implement
> something like this for ISC DHCPD, but I'm not sure if it'll be in
> this week's release (I suspect not, at this point).  If the latter,
> ISC DHCPD can be made to do what you want with minimal changes.
> 
> 			       _MelloN_
>