Configuration·LPIC-2
DHCP, and when not to start a service
Objective 210.1 is DHCP configuration. This guide reads how the client currently gets its address, writes a subnet declaration with a range and options, validates it with the syntax checker - and then explains why the service is left stopped on a network that already has a DHCP server.
202: Network Client Management Guide 17 of 29 Intermediate
- OSUbuntu 26.04 LTS
- Kernel7.0.0-30-generic
- systemd259
- Block devicesone 50 GB disk
- TimeAbout 19 min
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| LPIC2-A01 | 192.168.0.78 | Ubuntu 26.04 LTS | Primary service host - BIND, Apache, Samba, Postfix. Topic 204 RAID runs on loop devices; this machine has no spare disk | 2 Core | 4 GB | 50 GB |
| LPIC2-C01 | 192.168.0.80 | Ubuntu 26.04 LTS | Client - resolves, mounts and connects, so every service is proven from a machine that is not running it | 2 Core | 4 GB | 50 GB |
This guide includes
Use this for the DHCP objective, and for knowing when not to start something. This matters because a second DHCP server on a shared network breaks it for everyone - so this one is configured, validated and deliberately left stopped.
- finding how the client gets its address now, which is not DHCP
- writing a subnet declaration, and proving it parses before starting anything
- deciding to leave the service stopped, and why
Before you start
- what-stands-between-a-service-and-its-client
-
How the client gets its address now
-
A subnet declaration, and the checker that validates it
-
Why this one stays stopped