IETF Logo Mail Archive

Re: DHCP and secondaries

Ted Lemon <mellon@fugue.com> Wed, 15 May 1996 21:56 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01878; 15 May 96 17:56 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01872; 15 May 96 17:56 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa29555; 15 May 96 17:56 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA10998; Wed, 15 May 1996 17:52:38 -0400
Date: Wed, 15 May 1996 17:52:38 -0400
Message-Id: <199605152107.OAA28119@toccata.fugue.com>
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: Ted Lemon <mellon@fugue.com>
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

> 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_

v2.8.7 | Report a Bug | By Email