13,420
edits
Changes
Created page with '= Setting Up, Using & Maintaining a DHCP Server = Category:OPS235Category:OPS235 Labs ==Overview== * In this lab, you will learn how to setup, and run a DHCP server…'
= Setting Up, Using & Maintaining a DHCP Server =
[[Category:OPS235]][[Category:OPS235 Labs]]
==Overview==
* In this lab, you will learn how to setup, and run a DHCP server on your fedora3 machine, and then test-out the DHCP server by setting up your other VMs to receive an IP addresses from the DHCP server.
== Objectives ==
* To install, configure, and test ISC's DHCP Server.
* To obtain log information from DHCP server including lease address information.
* To lease the same IP address every-time from VM boot-up (instead of having DHCP server randomly assign IP address).
==Required Materials (Bring to All Labs)==
* Fedora 17 LIVE CD
* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
==Prerequisites==
* Completion and Instructor "Sign-off" of Lab 7: [[OPS235 Lab 7]]
==Linux Command Online Reference==
Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com]):
{|width="100%" cellpadding="5" width="50%"
|'''Networking Utilities:'''
|'''Additional Utilities:'''
|'''Configuration Files:'''
|- valign="top"
|
*[http://linuxmanpages.com/man8/dhcpd.8.php dhcpd]
*[http://linuxmanpages.com/man8/ifconfig.8.php ifconfig]
|
*[http://www.linuxcertif.com/man/1/systemctl/ systemctl]
*[http://linuxmanpages.com/man1/tail.1.php tail]
|
*[http://linuxmanpages.com/man5/dhcpd.conf.5.php dhcpd.conf]
*[http://linuxmanpages.com/man5/dhcp-options.5.php dhcpd-options]
*[http://linuxmanpages.com/man5/dhcpd.leases.5.php dhcpd.leases]
|}
==Resources on the web==
Additional links to tutorials and HOWTOs:
* [http://docs.fedoraproject.org/deployment-guide/f12/en-US/html/s1-dhcp-configuring-server.html Fedora DHCP Configuration Guide]
* [http://www.isc.org/software/dhcp Internet Software Consortium DHCP page]
== Install and Configure a DHCP Server ==
=== Lab Preparation ===
{{Admon/important | Update your systems | It is advisable to perform a <code>yum update</code> on your Fedora host and all 3 VM's.}}
{{Admon/important | Backup your VMs before proceeding | If you did not do it at the end of Lab 7, stop all of your VMs and backup your VM disk images.}}
{{Admon/note |ISC DHCP packages Overview | The version of DHCP server (rpm package name called '''dhcp-4.1.1-9.fc16.x86_64''' ) that comes with Fedora is maintained and distributed by the Internet Software Consortium (http://www.isc.org). The source package that you can download from ISC includes not only the DHCP server, but also a DHCP client and a DHCP relay agent. However, Fedora separates it into two RPM packages: the DHCP client package called '''dhclient-4.1.1-9.fc16.x86_64''' and the DHCP server package called '''dhcp-4.1.1-9.fc16.x86_64'''. The DHCP client package is installed by default by the workstation installation.}}
=== Investigation 1: How do you install the DHCP Server? ===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# To check that you have <code>dhclient</code> installed, enter the command:
:: <code>rpm -q dhclient</code>
<ol><li value="2"> If the package is not installed, you will get the message "package dhclient is not installed", otherwise, you will get the version information of the rpm package. Install the <code>dhclient</code> package if it was not installed.</li>
<li>Check to see if the <code>dhcp</code> server package is installed.</li>
<li>Follow the normal procedure to install the DHCP server rpm package called <code>dhcp</code> using <code>yum</code>.</li>
<li>Enter the command to list all the files installed from the DHCP server package.</li>
<li>What file appears to be a sample configuration file?</li>
<li>Copy the sample <code>dhcpd.conf</code> file to the <code>/etc/dhcp</code> directory making sure it is named <code>/etc/dhcp/dhcpd.conf</code></li>
</ol>
'''Answer the Investigation 1 observations / questions in your lab log book.'''
=== Investigation 2: What configuration options and directives need to be set in dhcpd.conf?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Study the man pages of <code>dhcpd</code>, <code>dhcpd.conf</code>, <code>dhcp-options</code>, and <code>dhcpd.leases</code> and make notes in your log book. In particular, look up the meaning and possible value(s), if any, for the following configuration options:
::* <code>broadcast-address</code>
::* <code>default-lease-time</code>
::* <code>max-lease-time</code> (How is this different from <code>default-lease-time</code>?)
::* <code>domain-name</code>
::* <code>domain-name-servers</code>
::* <code>fixed-address</code>
::* <code>group</code>
::* <code>hardware</code>
::* <code>host</code>
::* <code>host-name</code>
::* <code>range</code>
::* <code>routers</code>
::* <code>subnet</code>
::* <code>subnet-mask</code>
<ol><li value="2"> Study the sample <code>dhcpd.conf</code> file to see examples of how these options are used.</li>
</ol>
'''Answer the Investigation 2 observations / questions in your lab log book.'''
=== Investigation 3: How do I configure dhcpd settings to be applied to all subnets?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Edit <code>/etc/dhcp/dhcpd.conf</code> and examine the top section of the file.
# Make the following changes to the global settings:
::* <code>domain-name</code> should be set to '''ops235.org'''
::* <code>domain-name-servers</code> should be set to '''192.168.235.1'''
::* <code>default-lease-time</code> should be set to '''20 minutes'''
::* <code>max-lease-time</code> should be set to '''1 hour'''
<ol><li value="3">Save and exit your editing session.</li>
</ol>
{{Admon/note | Global Settings Affecting All Subnets | As global settings, these settings will affect <u>'''all subnets'''</u> unless they are separately declared for individual subnets.}}
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=== Investigation 4: How do I configure dhcpd to provide IP configuration to my virtual network?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Edit <code>/etc/dhcp/dhcpd.conf</code> for a second time, and add a new subnet delcaration for your virtual network
# The network address is '''192.168.235.0/255.255.255.0''' and the range of host addresses should be from '''51 to 60'''
# Also add a default gateway for the virtual network of '''192.168.235.1'''
# Save your editing session, and exit the text editor.
{{Admon/note | Recall Secure SSH Connection Method from Lab7 | Do not forget that you [http://zenit.senecac.on.ca/wiki/index.php/OPS235_Lab_7#Investigation_7:_How_do_you_make_sshd_more_secure. made ssh more secure] in the previous lab. Therefore, you will need to use the same command in lab7 to securely connect to your VM.}}
<ol><li value="5">Open another terminal window (ssh into fedora3 from fedora host as user root) and issue the following command:
::: <code>tail -f /var/log/messages</code>
<li>This will show you the last 10 lines of <code>/var/log/messages</code> continue to display new lines as they are added to the log.</li>
<li>In your original terminal prompt attempt to start the <code>dhcpd</code> service.</li>
<li>You should see new lines being added to the messages file.</li>
<li>If the <code>dhcpd</code> service fails to start any error messages will be logged in the messages file. Read the errors and attempt to fix your configuration file.</li>
<li>If the <code>dhcpd</code> service starts successfully you should see success messages in the log. </li>
<li>If your <code>dhcpd</code> service starts successfully, try to generate errors by editing the configuration file and introduce an error by removing a semicolon or closing curly bracket.</li>
<li>Restart your <code>dhcpd</code> service and observe the error messages generated. This is good practice to learn how to trouble-shoot and solve dhcpd errors.</li>
<li>Make certain that you have corrected those errors, and that your dhcpd service works properly.</li>
</ol>
{{Admon/tip | Troubleshooting Tip: | Troubleshooting produces the best results when you are methodical in your approach. Try to fix the first error mentioned before fixing subsequent errors. Often the first error may cause multiple error messages as the configuration file is parsed. When you think you have fixed the first error try to start your service and if it fails check the log again. Fix one error at a time.}}
'''Answer the Investigation 4 observations / questions in your lab log book.'''
=== Investigation 5: How do I test my dhcpd service on my virtual network?===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
# On a fedora3 terminal window make sure that the command <code>tail -f /var/log/messages</code> is running.
# On your fedora2 VM, change the configuration of '''eth1''' (or your interface name) to receive dynamic address configuration.
# Save your changes and restart the <code>NetworkManager</code> service.
# Observe the messages that get logged. You should see output similar to the following:
<pre >
Mar 24 13:28:24 fedora3 dhcpd: DHCPDISCOVER from 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPOFFER on 192.168.235.51 to 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPREQUEST for 192.168.235.51 (192.168.235.13) from 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPACK on 192.168.235.51 to 52:54:00:61:00:e7 via eth2
</pre>
{{Admon/note | Identifying DHCP Lease Transaction Information | These messages record the DHCP lease transaction that consists of 4 broadcast packets, DISCOVER, OFFER, REQUEST and ACKNOWLEDGE. Try researching on the internet how this transaction differs from a DHCP lease renewal.}}
<ol><li value="5">On fedora2, confirm the IP address assignment using <code>ifconfig</code></li>
</ol>
'''Answer the Investigation 5 observations / questions in your lab log book.'''
== Obtaining Lease Information & Lease Permanent IP Address ==
=== Investigation 6: Where does the dhcp server store a record of leased addresses?===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
# If your fedora3 DHCP server successfully issued the proper IP address configuration values to fedora2, check the file called <code>/var/lib/dhcpd/dhcpd.leases</code>
# You should see contents similar to:
<pre>
lease 192.168.235.51 {
starts 3 2010/03/24 17:28:25;
ends 3 2010/03/24 17:48:25;
cltt 3 2010/03/24 17:28:25;
binding state active;
next binding state free;
hardware ethernet 52:54:00:61:00:e7;
}
</pre>
{{Admon/note | Purpose of <code>dhcpd.leases</code> File | dhcpd records address leases in this file. If the service is restarted it reads in the file to know which addresses are currently leased and for how long.}}
<ol><li value="3">On the client fedora2 check the contents of the <code>/var/lib/dhclient</code> directory. The files in this directory is where the dhclient stores its record of leases.</li>
</ol>
'''Answer the Investigation 6 observations / questions in your lab log book.'''
=== Investigation 7: How can I lease the same address every time? ===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
{{Admon/note | Reserving IP Addresses with DHCP | Even though DHCP gives out IP address dynamically, it also has the ability to reserve an IP address for a certain computer. In this sense it's almost as if the client computer has a static IP even though it uses DHCP to get it. This is useful if you want to be able to put entries in your /etc/hosts file and not have to worry about the entry becoming invalid over time. In Linux we refer to this as supplying a fixed address to a host. Microsoft calls it a reservation.}}
# Make certain that you are located in your fedora3 virtual machine.
# Create a host declaration for fedora2. Make sure you record the correct <code>hardware ethernet</code> setting that corresponds to the MAC address of the interface in fedora2.
# Give it the fixed-address 192.168.235.12
{{Admon/tip | Avoiding IP Address Conflicts | When supplying fixed-address it is important that the address assigned is exclusive of any ranges that have been declared. Otherwise it may be possible for 2 different hosts to receive the same address.}}
<ol><li value="3">Start your service and test the address assignment by releasing your current address on fedora2 and then requesting a new address. Use the following commands on fedora2:</li>
</ol>
::: <code>ifdown eth1</code>
::: <code>ifup eth1</code>
<ol><li value="4">Confirm that you received the fixed address you were supposed to.</li>
</ol>
'''Answer the Investigation 7 observations / questions in your lab log book.'''
== Completing the lab ==
Arrange proof of the following on the screen:
* DHCP server log file showing a lease occuring
* DHCP server configuration file showing subnet and host declaration
* DHCP server lease file
* DHCP client lease file
== Preparing for Quizzes ==
# What protocol and port does dhcp use?
# What file is used to configure dhcpd?
# Can a dhcp server also be a dhcp client?
# What is the difference between max-lease-time and default-lease-time?
# What unit of measurement does default-lease-time require?
# What dhcp option is used for configuring a default gateway?
# What is the parameter range in the DHCP server configuration file used for?
# What is the purpose of a dhcp relay agent?
# Why might a dhcp relay agent be required?
[[Category:OPS235]][[Category:OPS235 Labs]]
==Overview==
* In this lab, you will learn how to setup, and run a DHCP server on your fedora3 machine, and then test-out the DHCP server by setting up your other VMs to receive an IP addresses from the DHCP server.
== Objectives ==
* To install, configure, and test ISC's DHCP Server.
* To obtain log information from DHCP server including lease address information.
* To lease the same IP address every-time from VM boot-up (instead of having DHCP server randomly assign IP address).
==Required Materials (Bring to All Labs)==
* Fedora 17 LIVE CD
* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
==Prerequisites==
* Completion and Instructor "Sign-off" of Lab 7: [[OPS235 Lab 7]]
==Linux Command Online Reference==
Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com]):
{|width="100%" cellpadding="5" width="50%"
|'''Networking Utilities:'''
|'''Additional Utilities:'''
|'''Configuration Files:'''
|- valign="top"
|
*[http://linuxmanpages.com/man8/dhcpd.8.php dhcpd]
*[http://linuxmanpages.com/man8/ifconfig.8.php ifconfig]
|
*[http://www.linuxcertif.com/man/1/systemctl/ systemctl]
*[http://linuxmanpages.com/man1/tail.1.php tail]
|
*[http://linuxmanpages.com/man5/dhcpd.conf.5.php dhcpd.conf]
*[http://linuxmanpages.com/man5/dhcp-options.5.php dhcpd-options]
*[http://linuxmanpages.com/man5/dhcpd.leases.5.php dhcpd.leases]
|}
==Resources on the web==
Additional links to tutorials and HOWTOs:
* [http://docs.fedoraproject.org/deployment-guide/f12/en-US/html/s1-dhcp-configuring-server.html Fedora DHCP Configuration Guide]
* [http://www.isc.org/software/dhcp Internet Software Consortium DHCP page]
== Install and Configure a DHCP Server ==
=== Lab Preparation ===
{{Admon/important | Update your systems | It is advisable to perform a <code>yum update</code> on your Fedora host and all 3 VM's.}}
{{Admon/important | Backup your VMs before proceeding | If you did not do it at the end of Lab 7, stop all of your VMs and backup your VM disk images.}}
{{Admon/note |ISC DHCP packages Overview | The version of DHCP server (rpm package name called '''dhcp-4.1.1-9.fc16.x86_64''' ) that comes with Fedora is maintained and distributed by the Internet Software Consortium (http://www.isc.org). The source package that you can download from ISC includes not only the DHCP server, but also a DHCP client and a DHCP relay agent. However, Fedora separates it into two RPM packages: the DHCP client package called '''dhclient-4.1.1-9.fc16.x86_64''' and the DHCP server package called '''dhcp-4.1.1-9.fc16.x86_64'''. The DHCP client package is installed by default by the workstation installation.}}
=== Investigation 1: How do you install the DHCP Server? ===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# To check that you have <code>dhclient</code> installed, enter the command:
:: <code>rpm -q dhclient</code>
<ol><li value="2"> If the package is not installed, you will get the message "package dhclient is not installed", otherwise, you will get the version information of the rpm package. Install the <code>dhclient</code> package if it was not installed.</li>
<li>Check to see if the <code>dhcp</code> server package is installed.</li>
<li>Follow the normal procedure to install the DHCP server rpm package called <code>dhcp</code> using <code>yum</code>.</li>
<li>Enter the command to list all the files installed from the DHCP server package.</li>
<li>What file appears to be a sample configuration file?</li>
<li>Copy the sample <code>dhcpd.conf</code> file to the <code>/etc/dhcp</code> directory making sure it is named <code>/etc/dhcp/dhcpd.conf</code></li>
</ol>
'''Answer the Investigation 1 observations / questions in your lab log book.'''
=== Investigation 2: What configuration options and directives need to be set in dhcpd.conf?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Study the man pages of <code>dhcpd</code>, <code>dhcpd.conf</code>, <code>dhcp-options</code>, and <code>dhcpd.leases</code> and make notes in your log book. In particular, look up the meaning and possible value(s), if any, for the following configuration options:
::* <code>broadcast-address</code>
::* <code>default-lease-time</code>
::* <code>max-lease-time</code> (How is this different from <code>default-lease-time</code>?)
::* <code>domain-name</code>
::* <code>domain-name-servers</code>
::* <code>fixed-address</code>
::* <code>group</code>
::* <code>hardware</code>
::* <code>host</code>
::* <code>host-name</code>
::* <code>range</code>
::* <code>routers</code>
::* <code>subnet</code>
::* <code>subnet-mask</code>
<ol><li value="2"> Study the sample <code>dhcpd.conf</code> file to see examples of how these options are used.</li>
</ol>
'''Answer the Investigation 2 observations / questions in your lab log book.'''
=== Investigation 3: How do I configure dhcpd settings to be applied to all subnets?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Edit <code>/etc/dhcp/dhcpd.conf</code> and examine the top section of the file.
# Make the following changes to the global settings:
::* <code>domain-name</code> should be set to '''ops235.org'''
::* <code>domain-name-servers</code> should be set to '''192.168.235.1'''
::* <code>default-lease-time</code> should be set to '''20 minutes'''
::* <code>max-lease-time</code> should be set to '''1 hour'''
<ol><li value="3">Save and exit your editing session.</li>
</ol>
{{Admon/note | Global Settings Affecting All Subnets | As global settings, these settings will affect <u>'''all subnets'''</u> unless they are separately declared for individual subnets.}}
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=== Investigation 4: How do I configure dhcpd to provide IP configuration to my virtual network?===
{{Admon/note | Use your fedora3 VM | Complete the following steps on your fedora3 VM.}}
# Edit <code>/etc/dhcp/dhcpd.conf</code> for a second time, and add a new subnet delcaration for your virtual network
# The network address is '''192.168.235.0/255.255.255.0''' and the range of host addresses should be from '''51 to 60'''
# Also add a default gateway for the virtual network of '''192.168.235.1'''
# Save your editing session, and exit the text editor.
{{Admon/note | Recall Secure SSH Connection Method from Lab7 | Do not forget that you [http://zenit.senecac.on.ca/wiki/index.php/OPS235_Lab_7#Investigation_7:_How_do_you_make_sshd_more_secure. made ssh more secure] in the previous lab. Therefore, you will need to use the same command in lab7 to securely connect to your VM.}}
<ol><li value="5">Open another terminal window (ssh into fedora3 from fedora host as user root) and issue the following command:
::: <code>tail -f /var/log/messages</code>
<li>This will show you the last 10 lines of <code>/var/log/messages</code> continue to display new lines as they are added to the log.</li>
<li>In your original terminal prompt attempt to start the <code>dhcpd</code> service.</li>
<li>You should see new lines being added to the messages file.</li>
<li>If the <code>dhcpd</code> service fails to start any error messages will be logged in the messages file. Read the errors and attempt to fix your configuration file.</li>
<li>If the <code>dhcpd</code> service starts successfully you should see success messages in the log. </li>
<li>If your <code>dhcpd</code> service starts successfully, try to generate errors by editing the configuration file and introduce an error by removing a semicolon or closing curly bracket.</li>
<li>Restart your <code>dhcpd</code> service and observe the error messages generated. This is good practice to learn how to trouble-shoot and solve dhcpd errors.</li>
<li>Make certain that you have corrected those errors, and that your dhcpd service works properly.</li>
</ol>
{{Admon/tip | Troubleshooting Tip: | Troubleshooting produces the best results when you are methodical in your approach. Try to fix the first error mentioned before fixing subsequent errors. Often the first error may cause multiple error messages as the configuration file is parsed. When you think you have fixed the first error try to start your service and if it fails check the log again. Fix one error at a time.}}
'''Answer the Investigation 4 observations / questions in your lab log book.'''
=== Investigation 5: How do I test my dhcpd service on my virtual network?===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
# On a fedora3 terminal window make sure that the command <code>tail -f /var/log/messages</code> is running.
# On your fedora2 VM, change the configuration of '''eth1''' (or your interface name) to receive dynamic address configuration.
# Save your changes and restart the <code>NetworkManager</code> service.
# Observe the messages that get logged. You should see output similar to the following:
<pre >
Mar 24 13:28:24 fedora3 dhcpd: DHCPDISCOVER from 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPOFFER on 192.168.235.51 to 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPREQUEST for 192.168.235.51 (192.168.235.13) from 52:54:00:61:00:e7 via eth2
Mar 24 13:28:25 fedora3 dhcpd: DHCPACK on 192.168.235.51 to 52:54:00:61:00:e7 via eth2
</pre>
{{Admon/note | Identifying DHCP Lease Transaction Information | These messages record the DHCP lease transaction that consists of 4 broadcast packets, DISCOVER, OFFER, REQUEST and ACKNOWLEDGE. Try researching on the internet how this transaction differs from a DHCP lease renewal.}}
<ol><li value="5">On fedora2, confirm the IP address assignment using <code>ifconfig</code></li>
</ol>
'''Answer the Investigation 5 observations / questions in your lab log book.'''
== Obtaining Lease Information & Lease Permanent IP Address ==
=== Investigation 6: Where does the dhcp server store a record of leased addresses?===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
# If your fedora3 DHCP server successfully issued the proper IP address configuration values to fedora2, check the file called <code>/var/lib/dhcpd/dhcpd.leases</code>
# You should see contents similar to:
<pre>
lease 192.168.235.51 {
starts 3 2010/03/24 17:28:25;
ends 3 2010/03/24 17:48:25;
cltt 3 2010/03/24 17:28:25;
binding state active;
next binding state free;
hardware ethernet 52:54:00:61:00:e7;
}
</pre>
{{Admon/note | Purpose of <code>dhcpd.leases</code> File | dhcpd records address leases in this file. If the service is restarted it reads in the file to know which addresses are currently leased and for how long.}}
<ol><li value="3">On the client fedora2 check the contents of the <code>/var/lib/dhclient</code> directory. The files in this directory is where the dhclient stores its record of leases.</li>
</ol>
'''Answer the Investigation 6 observations / questions in your lab log book.'''
=== Investigation 7: How can I lease the same address every time? ===
{{Admon/note | Use your fedora2 and fedora3 VMs | Complete the following steps on your fedora2 and fedora3 VM's.}}
{{Admon/note | Reserving IP Addresses with DHCP | Even though DHCP gives out IP address dynamically, it also has the ability to reserve an IP address for a certain computer. In this sense it's almost as if the client computer has a static IP even though it uses DHCP to get it. This is useful if you want to be able to put entries in your /etc/hosts file and not have to worry about the entry becoming invalid over time. In Linux we refer to this as supplying a fixed address to a host. Microsoft calls it a reservation.}}
# Make certain that you are located in your fedora3 virtual machine.
# Create a host declaration for fedora2. Make sure you record the correct <code>hardware ethernet</code> setting that corresponds to the MAC address of the interface in fedora2.
# Give it the fixed-address 192.168.235.12
{{Admon/tip | Avoiding IP Address Conflicts | When supplying fixed-address it is important that the address assigned is exclusive of any ranges that have been declared. Otherwise it may be possible for 2 different hosts to receive the same address.}}
<ol><li value="3">Start your service and test the address assignment by releasing your current address on fedora2 and then requesting a new address. Use the following commands on fedora2:</li>
</ol>
::: <code>ifdown eth1</code>
::: <code>ifup eth1</code>
<ol><li value="4">Confirm that you received the fixed address you were supposed to.</li>
</ol>
'''Answer the Investigation 7 observations / questions in your lab log book.'''
== Completing the lab ==
Arrange proof of the following on the screen:
* DHCP server log file showing a lease occuring
* DHCP server configuration file showing subnet and host declaration
* DHCP server lease file
* DHCP client lease file
== Preparing for Quizzes ==
# What protocol and port does dhcp use?
# What file is used to configure dhcpd?
# Can a dhcp server also be a dhcp client?
# What is the difference between max-lease-time and default-lease-time?
# What unit of measurement does default-lease-time require?
# What dhcp option is used for configuring a default gateway?
# What is the parameter range in the DHCP server configuration file used for?
# What is the purpose of a dhcp relay agent?
# Why might a dhcp relay agent be required?
