Changes

Jump to: navigation, search

OPS235 Lab 8 - Fedora17

1,238 bytes added, 18:38, 24 March 2010
no edit summary
* When you have successfully started your service answer the Investigation 4 question in your log book. You may want to include all of the syntax you used.
=== Investigation 5: How do I test my dhcpd service on my virtual network?==={{Admon/note | Note! | Complete the following steps on your fedora1 fedora2 and fedora3 VM's.}}
* On a fedora3 terminal window make sure that the command <code>tail -f /var/log/messages</code> is running.
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 | Note! | 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.}}
* On fedora2 confirm the IP address assignment using <code>ifconfig</code>
* Answer the Investigation 5 question in your log book.
 
=== Investigation 6: Where do the dhcp server and dhclient store a record of leased addresses?===
{{Admon/note | Note! | 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;
}
{{Admon/note | Note! | 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.}}
* On the client fedora2 check the file called <code>/var/lib/dhclient
9
edits

Navigation menu