IETF Logo Mail Archive

Re: DHCP and secondaries

Christopher Davis <chr+@andrew.cmu.edu> Thu, 16 May 1996 17:42 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19752; 16 May 96 13:42 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19748; 16 May 96 13:42 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa01032; 16 May 96 13:42 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA24264; Thu, 16 May 1996 13:39:23 -0400
Date: Thu, 16 May 1996 13:39:23 -0400
Message-Id: <4laq50q00UM9F6mFUr@andrew.cmu.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: Christopher Davis <chr+@andrew.cmu.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

Excerpts from netdev.dhcp-v4: 15-May-96 Re: DHCP and secondaries by John
Miezitis@its.utas.e 
> How does it support secondaries?  Do you have to maintain a list of
> secondary addresses and the associated primary addresses?

No matter what server implementation you make, you're going have tell
the dhcp server the topology of your network. In 3.3.8, if you don't
have secondaries, the dhcpd.conf for a relay agent looks like this:

network subnet5 128.2.5.0 255.255.255.0 both
gateway 128.2.5.126 255.255.255.0 subnet5

Were 128.2.5.126 is the relay agent, and the network number is
automatically generated using the mask.
With secondaries:

network subnet5 128.2.5.0 255.255.255.0 both
network subnet7 128.2.7.0 255.255.255.0 both
gateway 128.2.5.126 255.255.255.0 subnet5 subnet7
proxy 128.2.5.126 128.2.7.0 255.255.255.0

Most of our networks have secondaries, and it seems to be working fine for us.


Chris Davis
Network Development
Carnegie Mellon University

v2.8.7 | Report a Bug | By Email