How to Fix ‘Wi-Fi Has the Self-Assigned IP Address’ on Mac

The error notice “Wi-Fi has the self-assigned IP address [169.254.x.x] and will not be able to connect to the Internet” occurs in macOS when your Mac associates successfully with a wireless router or access point but fails to obtain a valid local IP address from the network’s Dynamic Host Configuration Protocol (DHCP) server. Because the router fails to assign standard private network parameters (such as 192.168.x.x or 10.0.x.x), macOS falls back to Automatic Private IP Addressing (APIPA), isolating the computer from local network resources and the internet. Resolving this issue involves renewing DHCP leases, purging corrupted configuration plists, and resetting network service configurations.

Why macOS Assigns Itself a 169.254.x.x IP Address

Under Internet Engineering Task Force (IETF) RFC 3927 standards, when an operating system interface establishes a link layer connection but receives no response to its DHCP Discover packets within a designated timeout window, it automatically assigns itself an address in the 169.254.0.1 to 169.254.255.254 range. While APIPA permits direct ad-hoc communication between two computers on the same physical link, it provides no gateway address or DNS routing to the public internet.

Common causes of this condition in macOS include:

• DHCP Server Pool Exhaustion: The local wireless router has allocated all available IP leases in its subnet pool, rejecting new connection requests.
• Corrupted macOS Network Configuration Files: Stale property list (.plist) files in the system configuration directory retaining broken interface definitions.
• Outdated Network Locations and Firewall Rules: Third-party security suites, VPN network filters, or stale virtual network interfaces blocking DHCP acknowledgment packets.
• MAC Address Filtering or WPA Handshake Mismatches: The Wi-Fi access point accepts the wireless security passphrase but isolates the client due to access control rules.

Layer	Normal State	Self-Assigned State
IP Addressing	192.168.1.X or 10.0.0.X (Assigned by Router)	169.254.X.X (Self-Generated via APIPA)
Default Gateway	Router IP (e.g., 192.168.1.1)	Blank / Undefined
DNS Nameservers	Provided via DHCP option 6	Unreachable or Unconfigured
Internet Access	Fully Routed	Blocked (Local link-only)

Step 1: Renew the DHCP Lease in macOS System Settings

The simplest way to resolve an APIPA assignment is to force macOS to broadcast a fresh DHCP request to the local router.

1. Click the Apple menu in the top-left corner and select System Settings.
2. Click Wi-Fi in the sidebar.
3. Next to your connected Wi-Fi network, click the Details button.
4. Select TCP/IP from the left-hand menu.
5. Ensure Configure IPv4 is set to Using DHCP.
6. Click the Renew DHCP Lease button, then click Apply.
7. Observe whether the IP address changes from 169.254.x.x to a valid subnet address (such as 192.168.1.15).

Step 2: Restart Your Router and Clear Stale Leases

If your router’s internal DHCP table is locked or out of available addresses, no client on the network can obtain an IP:

1. Unplug the power adapter from your wireless router or modem.
2. Wait 30 seconds to allow the volatile memory capacitors to discharge completely.
3. Plug the power cable back in and wait two to three minutes for the broadband handshake to establish.
4. Toggle Wi-Fi Off and On on your Mac to initiate a new connection handshake.

Step 3: Delete Corrupted macOS Network Configuration Plist Files

If macOS has stored invalid network interface parameters, clearing the system configuration cache forces the operating system to regenerate pristine network preferences.

1. Turn off Wi-Fi by clicking the Wi-Fi icon in the menu bar and toggling it Off.
2. Open Finder, click the Go menu at the top of the screen, and select Go to Folder….
3. Enter the following directory path and press Return:

/Library/Preferences/SystemConfiguration/

4. Locate and delete (or move to a backup folder on your Desktop) the following files:
   • com.apple.airport.preferences.plist
   • com.apple.network.identification.plist
   • NetworkInterfaces.plist
   • preferences.plist
5. Empty the Trash and restart your Mac.
6. Upon rebooting, macOS will recreate these files with default factory network parameters. Turn Wi-Fi back on and reconnect to your network.

Step 4: Create a New Network Location

Creating a clean network location flushes all legacy custom DNS, proxy, and routing configurations that may interfere with DHCP exchanges.

1. Open Terminal via Spotlight (press Cmd + Space and type Terminal).
2. Create a new network location named “HomeClean” using the network setup tool:

networksetup -createlocation HomeClean populate
networksetup -switchtolocation HomeClean

3. Return to System Settings > Wi-Fi, select your network, and verify whether a fresh IP lease is obtained.

Step 5: Set a Manual Static IP Temporarily to Test Connectivity

If the router’s DHCP server remains unresponsive, manually configuring a static IP within the router’s subnet allows you to verify hardware connectivity.

1. In System Settings > Wi-Fi > Details > TCP/IP, change Configure IPv4 from Using DHCP to Manually.
2. Assign an IP address outside your router’s typical allocation range (e.g., 192.168.1.195 if your router operates on 192.168.1.1).
3. Set the Subnet Mask to 255.255.255.0.
4. Set the Router to your gateway address (e.g., 192.168.1.1).
5. Navigate to the DNS tab and add public DNS servers: 1.1.1.1 and 8.8.8.8.
6. Click OK. If internet access functions immediately under static settings, the router’s DHCP daemon is either misconfigured or requires a firmware update.