Re: BOOTP clients with DHCP 'pool' functionality....?
Erikas Aras Napjus <firstname.lastname@example.org> Fri, 11 April 1997 15:55 UTC
Received: from cnri by ietf.org id aa16038; 11 Apr 97 11:55 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa12842; 11 Apr 97 11:55 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/188.8.131.52/17Jul96-0109PM) id AA27991; Fri, 11 Apr 1997 11:42:20 -0400
Date: Fri, 11 Apr 1997 11:42:20 -0400
From: Erikas Aras Napjus <email@example.com>
To: Multiple recipients of list <firstname.lastname@example.org>
Subject: Re: BOOTP clients with DHCP 'pool' functionality....?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Excerpts from netdev.dhcp-v4: 11-Apr-97 BOOTP clients with DHCP 'po.. by Justin Clark - I. UK@int > I have a couple of questions to pose to the group: > > 1> Any fundamental flaws in this? We've been doing it with our server since it's inception. So far we haven't run into any difficulties outside of the obvious eventual address exhaustion. Our server automatically tries to minimize IP address changes for both dynamic BOOTP and DHCP clients. (We also only do "dynamic BOOTP" for a fairly small portion of our network.) > 2> Can the static/dynamic table be in memory cache or should it be > committed to disk? We cache in memory, but dump to disk periodically. We do this with all of the normal lease information for both dynamic BOOTP and DHCP in case the process loses its own state. > 4> Are there any commercial or shareware vendors providing such a > capability? i.e a large corporate doesn't need to build a MAC/IP address > pair table for each client - the server dynamically builds the table > based on first allocations? We do it. I suspect others do as well. --- Erikas
- BOOTP clients with DHCP 'pool' functionality....? Justin Clark - Integralis UK
- Re: BOOTP clients with DHCP 'pool' functionality.… Erikas Aras Napjus
- Re: BOOTP clients with DHCP 'pool' functionality.… Kester Fong