Automatic allocation in dhcp-3.3.7
boris@hal2000.law.columbia.edu Mon, 20 May 1996 21:06 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25890;
20 May 96 17:06 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa25886;
20 May 96 17:06 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa13422;
20 May 96 17:06 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA03759; Mon, 20 May 1996 17:04:42 -0400
Date: Mon, 20 May 1996 17:04:42 -0400
Message-Id: <9605202004.AA12023@hal2000.law.columbia.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: boris@hal2000.law.columbia.edu
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Automatic allocation in dhcp-3.3.7
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Has anybody tried automatic allocation in dhcp-3.3.7?
If yes - how CMU dhcp defines the pool of IPs for automatic static (permanent)
allocation. As I understand it should be distinguished from dynamic one.
Is it like dynamic with unfinite lease? If so, then what is the value for dl
for "infinite"? Or, maybe, "dy" flag for static addresses shouldn't be set?
Thanks,
- Boris
===============================
Boris Niyazov
IT Department
Columbia Law School