Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
|
NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|
|
|
|
TCP/IP Bootstrap Protocol (BOOTP)
Before a device on a TCP/IP network
can effectively communicate, it needs to know its IP address. While
a conventional network host can read this information from its internal
disk, some devices have no storage, and so do not have this luxury.
They need help from another device on the network to provide them with
an IP address and other information and/or software they need to become
active IP hosts. This problem of getting a new machine up and running
is commonly called bootstrapping, and to provide this capability
to IP hosts, the TCP/IP Bootstrap Protocol (BOOTP) was created.
In this section I provide a fairly
detailed look at the TCP/IP Bootstrap Protocol. I begin with an overview
and history of the protocol and a look at the standards that define
it. I then discuss the general client/server nature of BOOTP and how
addressing is done in communication between the client and the server.
I describe the operation of BOOTP step by step, and illustrate the format
of BOOTP messages. I conclude with a description of BOOTP vendor extensions,
which are used to allow the information sent in BOOTP messages to be
customized, and a discussion of BOOTP relay agents, which allow the
protocol to operate even when the BOOTP server and client are on different
networks.
Related Information: BOOTP was the predecessor of the Dynamic Host Configuration Protocol. DHCP was built to be substantially compatible with BOOTP and so the two protocols have a fair degree of commonality. To avoid duplication, certain information has been included only in the DHCP section, with links provided from the BOOTP topics where appropriate. On the other hand, some of the historical background information behind features like vendor information extensions and relay agents, which were first developed for BOOTP and adopted by DHCP, is in this section and linked from the DHCP topics. Why structure the sections this way? DHCP is far more popular than BOOTP today, so I wanted its description to be complete, but some features only really make sense if initially explained in the context of BOOTPs operation.
If you plan to read about DHCP as well as BOOTP, I recommend reading this section first. If you don't plan to read up on DHCP, you may wish to check the topic in the DHCP topic on DHCP/BOOTP interoperability. |
Quick navigation to subsections and regular topics in this section
|
If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|