Re: DHCP and secondaries

Richard Letts <R.J.Letts@salford.ac.uk> Thu, 16 May 1996 16:53 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18102; 16 May 96 12:53 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18098; 16 May 96 12:53 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa26970; 16 May 96 12:53 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA21146; Thu, 16 May 1996 12:40:00 -0400
Date: Thu, 16 May 1996 12:40:00 -0400
Message-Id: <9605161603.AA19129@reef.bucknell.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: Richard Letts <R.J.Letts@salford.ac.uk>
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 PL23]

Mike Carney - Sun BOS Software wrote....
> 
> I'm curious - Are you subnetting Class B networks to class C, and find that 
> 254 addresses is not enough for one media segment, or do you have a number 
> of Class C addresses, and must use multiple logical networks on the same 
> media the service the number of hosts you've got out there?
> 
The campus network hert is *very* routed. with an average of 40 hosts/subnet
we have a 'normal' subnet mask of 255.255.255.128

some networks have grown more than they were supposed to, and we have had to
expand the subnet range on the cable; in general this is by either changing
the subnet mask for the hosts on the cable, or in the first instance making
the next address-range on the cable the primary and the existing rang the
secondary.

eg.  146.87.253.0 ran out of addresses.

1. make 146.87.253.0 the secondary network number on the router
2. make 146.87.253.128 the primary network number on the router
3. change the subnet mask to be 255.255.255.0 on other devices on the network
4. wait until everthing agrees what the subnet-mask is now
5. make 146.87.253.0/255.255.255.0 the network/mask for the network on the
router.

[I tell departments not to use the .128 networks in their initial setup to
allow them flexibility to do this later]

Of course this falls-down when you come across a host that doesn't
understand subnetworks (we still have some this stupid), then it has
to go somewhere proxy-arp is supported.

As the network topology is getting flattened we're ending up with multiple
networks on the same cable that have no relationship; in this case we tell
everything that the mask is 255.255.0.0, and rely on proxy-arp.

Richard Letts  
-------------------------------------------------------------------------------
Network Manager                               mail:    R.J.Letts@salford.ac.uk  
University of Salford                         phone:     +44 161 745 5252
Great Britain                                 fax:       +44 161 745 5888