What should happen
DHCP clients broadcast Discover; a server or relay answers Offer; the client Requests; the server Acknowledges with address, mask, gateway, DNS, and lease time. When any leg vanishes, the client keeps a link-local or stale address—symptoms look like “Wi-Fi connected, no internet.”
Capture and commands
| Perspective | What to run | Looks for |
|---|---|---|
| Client Linux | journalctl -u NetworkManager -f or dhcpcd -d | NAK, timeout, rogue server |
| Wire sniff | tcpdump -ni eth0 port 67 or port 68 | Discover without Offer, duplicate MAC |
| Server | Lease file / SQL / Kea logs | Pool exhaustion, class mismatch |
| Relay | Verify giaddr and circuit-id | Wrong VLAN mapped to scope |
Windows quick checks
ipconfig /all shows DHCP enabled state and server ID; ipconfig /renew forces a new cycle—pair with a simultaneous capture on the default gateway port if possible.
Related: what is DHCP relay, DHCP scope, IP lease, DNS troubleshooting commands.