Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases
The DHCP server has no unused addresses left in the scope.
no free leasesDHCPDISCOVER no free leasesdhcpd: network no free leasesDHCP pool exhaustedDHCP address pool full Meaning
Increase the pool or shorten the lease time (guests and phones fill small pools), remove stale reservations, find devices flooding with random MACs, and check for a DHCP-starvation attack. Reduce lease time from days to hours on guest networks.
Common causes
- Pool too small for the number of devices
- Very long lease times on a busy network
- Many stale leases or random-MAC devices
- DHCP starvation attack
- Static devices inside the dynamic range
⚡ Quick fix
- Enlarge the range or use a bigger subnet
- Shorten lease times
- Clear stale leases and enable DHCP snooping/limits
Detailed fix by platform
Linux
- bash
sudo journalctl -u isc-dhcp-server | grep "no free leases" sudo dhcp-lease-list | wc -l
How to diagnose
- Free leases — None?
- Lease time — Too long?
- Clients — Unexpected spike?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 169.254.x.x self-assigned IP (DHCP failed) Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026