DHCP is a shared network control service: a small mismatch between an interface, subnet declaration, and address policy can prevent every new client from connecting. This hands-on course teaches you to configure those pieces deliberately and diagnose the service from configuration, logs, packets, and lease state.
You will install ISC DHCP Server, bind it to an interface, define pools and client options, reserve an address by MAC, and inspect persistent leases. You will also observe a DORA exchange on an isolated virtual link before building and validating a complete office-network policy.
What You Will Learn
- Install ISC DHCP Server, select an IPv4 interface, and start the service safely
- Match an interface address to the correct subnet and dynamic address pool
- Distribute router and DNS options and define default and maximum lease times
- Reserve a fixed address for a known MAC outside the dynamic pool
- Read and filter
dhcpd.leasesto relate addresses, clients, and expiry times - Generate and recognize Discover, Offer, Request, and Acknowledge traffic
- Combine
journalctl,tcpdump, syntax validation, and service status to troubleshoot failures
Who This Course Is For
This intermediate course is for Linux administrators, DevOps and networking learners, support engineers, and lab operators who need to provision IPv4 clients from a central server. It is especially useful if you understand subnets but have not yet translated them into a DHCP scope, reservation, lease policy, and troubleshooting workflow.
Prerequisites: Basic Linux terminal, IPv4 subnetting, interfaces, services, file-editing, and sudo skills. Familiarity with MAC addresses and packet capture is helpful.
Learning environment: A Debian/Ubuntu-style LabEx Linux terminal with ISC DHCP Server, prepared eth0 and isolated veth interfaces, dhclient, tcpdump, and synthetic lease/log data.
Frequently Asked Questions
Will the DHCP exercises disrupt the lab machine's main network connection?
The live client transaction uses an isolated veth-client/veth-server link and deliberately omits a default gateway, so it does not replace the VM's primary route. Other exercises use prepared simulated subnets and interfaces within the lab environment.
How is a DHCP reservation different from configuring a static IP on the device?
With a reservation, the client still requests configuration through DHCP, but the server recognizes its MAC address and always offers the specified IP. The guided printer uses .50 outside the .100–.200 pool, and the final office printer uses 192.168.10.5 outside its dynamic pool.
Does the final challenge prove that a real client received a lease?
No. The final challenge proves syntax validity and a running service for the 192.168.10.0/24 policy. The earlier lease-analysis lab is where you run dhclient -v, observe DORA, and confirm the new transaction in dhcpd.leases. DHCPv6, relays, failover, and multiple-server design are not covered.
