Router Not Assigning IP Addresses? Fix DHCP Issues Fast

What is the DHCP DORA Handshake?

The Dynamic Host Configuration Protocol (DHCP) operates at the Application Layer of the TCP/IP suite. It dynamically delegates IP parameters to local devices, avoiding manual configurations. This lease allocation process follows a four-step handshake, often referred to as **DORA**:

• Discover (Client to Broadcast): When a client device connects to the network (physical cable insertion or Wi-Fi association), it does not have an IP. It broadcasts a DHCPDISCOVER packet containing its hardware MAC address over UDP port 68 to destination 255.255.255.255.
• Offer (Router to Client): The router's DHCP daemon (listening on UDP port 67) receives the broadcast. It checks its active lease tables, reserves an available IP, and unicasts or broadcasts a DHCPOFFER packet containing the proposed IP, subnet mask, default gateway, DNS servers, and lease duration.
• Request (Client to Router): The client receives the offer. If multiple offers are received (due to rogue routers), it selects one and broadcasts a DHCPREQUEST packet, letting all servers know it has accepted the specific offer.
• Acknowledge (Router to Client): The chosen router receives the request, binds the client's MAC address to the leased IP, and returns a DHCPACK packet to confirm the lease is active.

Why Do Devices Fall Back to a 169.254.x.x APIPA IP?

If a client device broadcasts a DHCPDISCOVER packet but receives no reply within its timeout window, the operating system invokes **APIPA** (Automatic Private IP Addressing). APIPA is a fallback protocol defined by RFC 3927 that assigns a temporary link-local IP in the range **169.254.1.0 to 169.254.254.255** with subnet mask **255.255.0.0**.

An APIPA IP allows you to communicate with other local devices that also failed to obtain an IP. However, because APIPA has no default gateway parameter, devices cannot route packets beyond their immediate local link. The appearance of a 169.254.x.x IP address is confirmation that the DORA handshake failed, typically due to a crashed router DHCP service or signal attenuation.

Step-by-Step Settings Optimization by Brand

If you need to verify or configure your router's DHCP server settings, follow these instructions for the major residential router brands:

1. TP-Link (Tether App / Web UI)

Log into the web dashboard (192.168.0.1 or tplinkwifi.net). Go to **Advanced** → **Network** → **DHCP Server**. Verify that the DHCP Server checkbox is selected. Check the IP Address Pool range (ensure it supports enough devices, e.g. 100 to 249). Set the Address Lease Time to 120 minutes (for high turnover networks) or 1440 minutes (default 24 hours).

2. ASUS (ASUSWRT console)

Go to **Advanced Settings** → **LAN** → **DHCP Server** tab. Enable the DHCP Server toggle. You can set the IP pool range and configure **Manual Assignment** (MAC binding) at the bottom of the page.

3. Netgear (Nighthawk / Orbi)

Go to **Advanced** → **Setup** → **LAN Setup**. Ensure the **Use Router as DHCP Server** checkbox is selected. You can set the start and end IP addresses and configure static address reservations here.

4. Linksys

Go to **Connectivity** → **Local Network** → **DHCP Server**. Toggle the DHCP Server to Enabled, adjust the client lease time, and save your changes.

Hardware Failures Causing DHCP Drops

If a router continues to drop DHCP allocations even after a factory reset and with minimal devices connected, the hardware itself may be failing:

• RAM Degradation:The DHCP lease table is maintained in the router's system RAM. If the RAM chips degrade due to voltage fluctuations or age, data writes to the lease tables can fail, causing the DHCP service to crash.
• Thermal Throttling of the Switch SoC: Many home routers are fanless and rely on small passive heatsinks. If the router is placed in an unventilated area, the switch chip can overheat. This causes the router to drop packets and fail to process DHCP broadcasts, even while maintaining active LED link lights.
• Physical Port and PHY Chip Faults: Power surges can damage the physical Ethernet PHY transceiver chips behind the LAN ports. This damage can prevent client handshake frames from reaching the CPU, preventing the DHCP server from receiving the Discover request.
• Capacitor Aging:Swollen or failing electrolytic capacitors on the router's mainboard can cause voltage instability, leading to random CPU resets and crashes of network daemons like the DHCP service.

How ISPs Detect DHCP Issues Remotely

Internet Service Providers monitor network equipment performance up to your home gateway using several telemetry tools:

• CMTS Loop Diagnostic Logging: On cable networks, the **Cable Modem Termination System (CMTS)** monitors downstream DOCSIS channels. If a client router generates broadcast storms (e.g., from an STP network loop), the CMTS logs an alert and may throttle the connection to protect the node.
• DHCP IP Lease Expiry Telemetry: ISP routers check RADIUS and DHCP server logs for lease request patterns. If your router stops sending DHCP Request packets before its WAN lease expires, the ISP systems will log a provisioning timeout and mark the connection as offline.
• Modem SNMP Poll Errors: ISPs use Simple Network Management Protocol (SNMP) to poll modems and ONT units. If the ONT reports high packet drop rates on its Ethernet port, it indicates a link negotiation issue between the modem and your primary router.

When to Replace Your Router

Troubleshooting can only resolve configuration errors. If your router displays the following symptoms, it is time to replace the hardware:

• Recurring DHCP Crashes: The router stops assigning IP addresses every 24 to 48 hours, requiring a physical power cycle to restore network connectivity.
• NVRAM Write Errors: Settings changes, static IP reservations, or custom DNS configurations revert to default values after the router is rebooted.
• High Thermal Output: The router chassis feels hot to the touch, and throughput speeds drop under heavy network load.