Re: Which servers support secondary network numbers?

"James E. Drews" <drews@engr.wisc.edu> Fri, 16 August 1996 19:27 UTC

Received: from ietf.org by ietf.org id aa27943; 16 Aug 96 15:27 EDT
Received: from cnri by ietf.org id aa27939; 16 Aug 96 15:27 EDT
Received: from [134.82.7.6] by CNRI.Reston.VA.US id aa12748; 16 Aug 96 15:27 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA23725; Fri, 16 Aug 1996 15:23:51 -0400
Date: Fri, 16 Aug 1996 15:23:51 -0400
Message-Id: <199608161911.OAA16735@engr.wisc.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.org
From: "James E. Drews" <drews@engr.wisc.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Which servers support secondary network numbers?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Pegasus Mail for Win32 (v2.42a)

Cisco (and others I am sure) can can assign more than one ip range to
each port/wire.  For example, on one port of a Cisco router you can
assign the ip range:  144.92.4.0 (subnet mask 255.255.255.128). Then
sometime down the road when you add more machines to this network and you
need more IP addresses, Cisco (and others) will let you add a second
address range to the same wire.  The catch is, when a DHCP/BOOTP request
gets forwarded on from the NEW range, usually the gateway address in the
packet will be from the original range.  This causes DHCP/BOOTP servers
to assume the incorrect address range for the machine.  Some servers
DHCP/BOOTP have worked arround this problem.

Is that enough elaboration?

Jim

On 16 Aug 96 at 14:39, Hiroto Shibuya wrote:
> I'm afraid I don't really understand the functionality described here.
> Could you elaborate more on that?
> 
> On 16 Aug 96 at 12:30, John M. Wobus wrote:
> > I'd like to add information to the DHCP FAQ listing which servers can
> > handle "secondary addresses on router interfaces".  
>