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.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Network Configuration and Management Protocols (BOOTP, DHCP, SNMP and RMON)
           9  Host Configuration and TCP/IP Host Configuration Protocols (BOOTP and DHCP)

Previous Topic/Section
Host Configuration and TCP/IP Host Configuration Protocols (BOOTP and DHCP)
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Bootstrap Protocol (BOOTP)
Next Topic/Section

Host Configuration Concepts, Issues and Motivation
(Page 1 of 3)

Putting a host on an internetwork requires that certain setup and configuration procedures be followed. Hardware must be selected and set up, and software too must be chosen and installed on the hardware. Once the software is set up, we aren't finished, however: we must also perform other configuration tasks that tell the software how we want it to operate, and give it certain parameters so it knows its role on the network and how to function.

The Purposes of Host Configuration

Probably the most important configuration task that must be performed for each host on an internetwork is to give it an identity, in the form of an address that is unique to it alone. In TCP/IP networks, each device must be given an IP address. Hosts also often require other parameters to ensure that they operate properly. For a TCP/IP network, we might want to tell each host some of the following:

  • The address of a default router on the local network.

  • The network mask the host should use.

  • The addresses of servers providing particular services to the host, such as a mail server or a DNS name server.

  • The maximum transmission unit (MTU) of the local network.

  • What Time To Live (TTL) value to use for IP datagrams.

And possibly, a lot more; there are dozens of different parameters that must be set up for certain networks. Many of these may be common to all the machines on a network, but IP addresses must be unique. The administrator must therefore ensure that each is assigned to only one computer, even as machines are added to and removed from the network.

The Inefficiency of Manual Host Configuration

If you're an administrator in charge of a small ten-host LAN, performing setup and configuration is simple: for each host, you set up the hardware, install the software, and then configure the software. Even changes and keeping track of IP addresses wouldn't be a big deal; a single sheet of paper would suffice. However, what happens when your network has not ten computers but a hundred? How about a thousand? Ten thousand?

As the size of the network grows, the work needed for manual configuration grows with it. And while initial hardware setup may be time-consuming, at least it is done mainly when the host is first set up, and rarely changed thereafter. This is not the case with configuration parameters. If the address of the local router changes on a network with a thousand hosts, do you really want to go to each host to edit a configuration file? I sure don't!


Previous Topic/Section
Host Configuration and TCP/IP Host Configuration Protocols (BOOTP and DHCP)
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Bootstrap Protocol (BOOTP)
Next Topic/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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



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.