Re: DHCPINFORM _vs_ INIT-REBOOT
Shawn Mamros <mamros@ftp.com> Fri, 18 October 1996 14:24 UTC
Received: from cnri by ietf.org id aa19857; 18 Oct 96 10:24 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa11605;
18 Oct 96 10:24 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA13493; Fri, 18 Oct 1996 10:14:39 -0400
Date: Fri, 18 Oct 1996 10:14:39 -0400
Message-Id: <199610181344.JAA11049@MAILSERV-2HIGH.FTP.COM>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Shawn Mamros <mamros@ftp.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCPINFORM _vs_ INIT-REBOOT
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
I wrote: >[...] The only reason DHCPINFORM >exists is to allow systems which already have a permanent, pre-assigned >IPv4 address that was NOT obtained via DHCP to obtain configuration >information *other than* their IPv4 address. And only just now realized I forgot something: DHCPINFORM is also useful for cases where a temporary IP address is assigned through some means other than DHCP. The most common example of this is dial-up hosts which use PPP and obtain their IPv4 address via IPCP. The general rule of thumb is, if you used DHCP to obtain a leased address, you don't need (and shouldn't use) DHCPINFORM. It certainly isn't appropriate for confirming a previously-leased address at reboot time; that's what INIT-REBOOT is for. Hope this helps... -Shawn Mamros E-mail to: mamros@ftp.com
- DHCPINFORM _vs_ INIT-REBOOT Don Coolidge
- Re: DHCPINFORM _vs_ INIT-REBOOT Charles Ragan
- Re: DHCPINFORM _vs_ INIT-REBOOT Shawn Mamros
- Re: DHCPINFORM _vs_ INIT-REBOOT Shawn Mamros