Re: question about dhcp & secondary IP address
"Michael J. Lewis" <hosmjl@chevron.com> Tue, 28 May 1996 16:33 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18581;
28 May 96 12:33 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18577;
28 May 96 12:33 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa10429;
28 May 96 12:33 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA24817; Tue, 28 May 1996 12:17:40 -0400
Date: Tue, 28 May 1996 12:17:40 -0400
Message-Id: <31AB22C9.F9E@chevron.com>
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: "Michael J. Lewis" <hosmjl@chevron.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: question about dhcp & secondary IP address
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: Mozilla 2.0 (Win95; I)
> We use Windows NT 3.51 sever as DHCP sever. > We tested DHCP function successfully with Primary IP address. > But, When We tested this function with Secondary Ip address in our router ehternet port, > this DHCP function does not work. Microsoft's server will give out addresses only to the range that corresponds to its interface. If your server is on the physical wire with the secondaries, you will need either multiple cards in the server (one for the primary and each secondary) or multiple servers (one for the primary and each secondary). FYI, you will get some interesting responses on reboots when the client requests to continue using an address. The client's server will ACK the request while the others on the other subnet will NAK it. If a NAK arrives first, the client will go through the DISCOVER process to "reuse" its address. It is also possible to manipulate subnet masks on the server to fake it in to thinking it is processing one subnet. If this is done, all machines that need to talk with each other better be using the same subnet mask. If the server is across a router from the client, then the server will only be able to give out addresses on the primary subnet because that is what the router will stamp on packets sent to the server.
- question about dhcp & secondary IP address Christopher Shin
- Re: question about dhcp & secondary IP address Michael J. Lewis
- Re: question about dhcp & secondary IP address Tim Sylvester
- Re: question about dhcp & secondary IP address Ted Lemon