Date: Tue, 1 Apr 2014 13:22:18 -0400 From: Rick Miller <vmiller@hostileadmin.com> To: Dave Duchscher <daved@tamu.edu> Cc: Robert Huff <roberthuff@rcn.com>, net@freebsd.org Subject: Re: questions about (system) dhclient Message-ID: <CAHzLAVEMZoYw4hE3eLwYHEoC5usqxGyoH7u_Rw-LEEU4Ka%2BEMg@mail.gmail.com> In-Reply-To: <628086E4-3832-4221-B33E-9AC9234F3076@tamu.edu> References: <5339D0A0.1030903@rcn.com> <CAHzLAVGGR--GzG%2BzO80HLwPh-88e-2LswP5kaLHya1UqV1Kp6g@mail.gmail.com> <628086E4-3832-4221-B33E-9AC9234F3076@tamu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 1, 2014 at 10:46 AM, Dave Duchscher <daved@tamu.edu> wrote: > On Apr 1, 2014, at 7:48 AM, Rick Miller <vmiller@hostileadmin.com> wrote: > > > > > > The conversation between a DHCP server and client consists of the initial > > DHCP DISCOVER request from the client broadcasted to the network to > which a > > DHCP ACK is expected in reply from an available DHCP server. Upon > receipt > > of DHCP ACK, the client sends another DHCP DISCOVER to the server asking > > for configuration information necessary to initialize networking. The > > server's response is a DHCP OFFER containing all the information > requested > > by the client. > > > > I illustrate this in a sequence diagram describing a PXE workflow for > > FreeBSD installation at > > http://hostileadmin.com/images/FreeBSD_PXE_Install_Workflow.gif. The > first > > four steps in the sequence is the workflow's first DHCP conversation. > > > The description of the DHCP packet flow is incorrect. DHCP packet flow > is the following for clients requesting a new lease. Diagram below > copied from RFC 2131. For clients renewing a lease, only the REQUEST and > ACK steps are done. > Thanks, Dave...I did mix up the terminology. -- Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVEMZoYw4hE3eLwYHEoC5usqxGyoH7u_Rw-LEEU4Ka%2BEMg>