How to Fix WiFi Dropping After MacBook Wakes From Sleep: macOS Wake Settings, Adapter Power Management, and DHCP Lease Renewal Fixes

Opening a MacBook and waiting 10–30 seconds for WiFi to reconnect — or losing internet entirely until you toggle WiFi off and on — is one of the most common macOS networking complaints. The problem is reproducible and fixable. macOS suspends the WiFi adapter during sleep to save power, and when the system wakes, the adapter does not always rejoin the network cleanly. An expired DHCP lease, a stale IP address conflict, or a misbehaving VPN client can each cause the same symptom. Work through the fixes below in order; most users resolve the issue within the first three steps. Once your connection is stable, run a speed test to confirm you’re getting the throughput your plan provides.

Why macOS WiFi Drops After Sleep

When a MacBook enters sleep, macOS suspends the CPU, WiFi chipset, and most background services. Active TCP/UDP sessions are terminated, and the DHCP client stops sending keep-alive packets. If the sleep lasts longer than the router’s DHCP lease renewal window — typically 30 minutes to 24 hours depending on the router — the IP address is reclaimed. On wake, the Mac attempts to rejoin the network and request a new lease, but timing conflicts between the adapter coming online and the DHCP handshake completing can leave the device with no valid IP address. On M-series MacBooks (M1 through M4), Power Nap and Low-Power Mode add another layer: the WiFi hardware can enter a firmware-level suspend state that requires a full interface reset to recover from.

Fix 1: Disable “Wake for Network Access” (or Enable It)

This setting is counterintuitive. On Intel MacBooks used at a desk, enabling Wake for network access keeps the WiFi adapter partially active during sleep, which prevents the clean reconnect problem. On Apple Silicon MacBooks (M1–M4) running on battery, the same setting can conflict with the chip’s own power management and cause worse wake behavior — disabling it often resolves the drop.

1. Open System Settings › Battery › Options.
2. Find Wake for network access and toggle it. If it is currently on, turn it off. If it is off, turn it on.
3. Put the Mac to sleep for two minutes, wake it, and test immediately.

On plugged-in desktop Macs, keep this setting enabled. On MacBooks running on battery, try disabled first.

Fix 2: Enable TCP Keepalives to Prevent Adapter Sleep

macOS ships with a pmset setting that keeps the WiFi adapter alive during sleep by sending periodic TCP keepalive packets. On some MacBook models, this setting is off by default. Open Terminal and run:

sudo pmset -a tcpkeepalive 1

Enter your admin password when prompted. This tells macOS to maintain network keepalives even during sleep, which prevents the adapter from fully suspending. The -a flag applies the setting for both battery and AC power. To confirm the setting stuck, run pmset -g and look for tcpkeepalive 1 in the output.

Fix 3: Reset the WiFi Interface Manually

If your Mac wakes and shows WiFi connected but no internet — the adapter rejoined the network but failed to get a valid IP — a manual interface reset forces a clean restart of the network stack. In Terminal:

sudo ifconfig en0 down && sleep 5 && sudo ifconfig en0 up

This brings the WiFi interface down, waits five seconds, then brings it back up. macOS will immediately scan, associate, and perform a fresh DHCP handshake. On most MacBooks the interface is en0; to confirm yours, run ifconfig and look for the interface with a ssid line.

If you need to do this regularly, you can save the command as a shell alias or a Shortcut that runs AppleScript. A permanent fix is more useful, so continue through the remaining steps.

Fix 4: Renew Your DHCP Lease

After waking, if the Mac has an IP address that starts with 169.254.x.x (a self-assigned address), it failed to get a lease from the router. Force a renewal:

1. Open System Settings › Network › select your WiFi connection › Details.
2. Click the TCP/IP tab.
3. Click Renew DHCP Lease.
4. Click OK and close Settings.

If renewal succeeds, you will see a valid 192.168.x.x or 10.x.x.x address replace the 169.254 address within a few seconds. If it fails repeatedly, the issue may be on the router side — see Fix 6 below.

Fix 5: Forget and Rejoin the Network

A corrupted WiFi network profile can cause persistent wake failures even when the adapter and DHCP handshake are both working. Removing the saved network forces macOS to create a fresh profile:

1. Open System Settings › Network › Wi-Fi.
2. Click the Details button next to your network name.
3. At the bottom of the dialog, click Forget This Network and confirm.
4. Rejoin the network by selecting it from the WiFi menu and entering the password.
5. In Details, verify that Auto-Join is enabled so the Mac reconnects automatically on every wake.

Also ensure your router is not broadcasting on WPA3-only security mode. Some MacBook WiFi drivers on older macOS versions struggle to rejoin WPA3-only networks after sleep. Setting the router to WPA2/WPA3 Mixed — available on TP-Link, ASUS, Netgear, and eero — resolves this without downgrading security.

Fix 6: Increase DHCP Lease Duration on Your Router

If your router issues short DHCP leases (30 minutes is common on some ISP-provided gateways), a MacBook that sleeps longer than that will wake to an expired lease and stall while requesting a new one. Extending the lease duration gives the Mac more time before the IP is reclaimed:

• TP-Link routers: Advanced › Network › DHCP Server › Address Lease Time. Set to 1440 minutes (24 hours) or longer.
• ASUS routers: LAN › DHCP Server › IP Pool Lease Time. Set to 86400 seconds (24 hours).
• Netgear routers: Advanced › Setup › LAN Setup › Address Reservation or DHCP pool › Lease. Default is often 1440 minutes; confirm it has not been set lower.
• eero: DHCP lease time is managed automatically and is not user-adjustable; the eero system handles renewals on wake without user intervention in most cases.

For MacBooks that sleep overnight, a 24-hour lease duration is the practical minimum to avoid wake-related DHCP failures. Our guide on reading router system logs can help you confirm that lease renewals are completing successfully after each wake event.

Fix 7: Check for Third-Party Software Conflicts

VPN clients, firewall apps (such as Little Snitch or Lulu), and network monitoring tools install kernel extensions that intercept network traffic. A poorly behaved extension can prevent the WiFi stack from completing its wake sequence. If the drop started appearing after installing one of these tools, temporarily disable or uninstall the software and test sleep-wake behavior for 24 hours. Common culprits include:

• Corporate VPN clients (Cisco AnyConnect, GlobalProtect, Zscaler) that attempt to reconnect before the adapter is fully online
• DNS-over-HTTPS proxies that cache a stale server binding from before sleep
• Antivirus or endpoint security tools that scan network interfaces at wake

If removing the software resolves the issue, check the vendor’s support pages for a known macOS sleep/wake fix or update. Most major VPN vendors released sleep-aware updates for Apple Silicon in 2023–2024; running an outdated version on an M-series MacBook is a common hidden cause.

Fix 8: Reset NVRAM and SMC (Intel Macs Only)

On Intel MacBooks, low-level power management state is stored in NVRAM and managed by the System Management Controller (SMC). Corrupted SMC state can prevent the WiFi adapter from initializing correctly after sleep. To reset:

• NVRAM: Shut down. Press the power button, then immediately hold Option + Command + P + R for about 20 seconds. Release when you hear the startup chime twice (on older models) or see the Apple logo appear and disappear twice (on newer Intel models).
• SMC: Shut down. For MacBooks with a T2 chip, hold Control + Option + Shift for 7 seconds (without pressing power), then add the power button and hold all four keys for another 7 seconds. Release, wait 5 seconds, and power on normally.

On Apple Silicon MacBooks (M1–M4), there is no separate SMC or traditional NVRAM reset. Equivalent low-level resets happen automatically on restart — a clean shutdown and restart achieves the same result.

Summary: Fix Order

For most MacBook users, the sleep-wake WiFi drop resolves within the first three steps: toggling the Wake for Network Access setting, enabling tcpkeepalive via Terminal, and extending the DHCP lease on the router. If those do not resolve it, the forgotten-and-rejoined network profile or a third-party VPN conflict is almost always responsible. Run a speed test after resolving the issue to confirm your connection is delivering the speeds your plan provides — a clean reconnect should show full throughput with no packet loss artifacts from the sleep cycle.