Advertisement

eero mesh Wi-Fi stops working with static IP

If eero Wi‑Fi still connects but a device loses internet or local access after you set a static IP, the manual address is usually the problem, not the mesh link. This article helps you tell a bad device setting from an eero LAN issue and fix it fast.

Networking 10 min read
A white mesh Wi‑Fi router sits on a desk in a home office.

If eero Wi‑Fi still connects but a device loses internet or local access after you set a static IP, the manual address is usually the problem, not the wireless link. In this context, “static IP” can mean either a manual address set on the device itself or an eero DHCP reservation; for most home devices, the reservation is the safer choice. The usual fix is to move the device back to DHCP, then use an eero reservation if you still want the same address every time.

What usually breaks when eero and static IP stop playing nicely

The break is usually in the network path after the device joins Wi‑Fi. The Wi‑Fi link itself often still works. The device can still show as connected to eero, but it cannot reach the internet, printers, a NAS, or other local devices because its manual IP no longer fits the network it joined.

A common case is that someone copied an old static IP from a previous router and never updated it. That can look fine at first. Then it fails after the home network moves to eero, or after the eero gateway gets a different LAN range. eero support also notes that when the network is offline, the cause can be connectivity issues, misconfiguration, or a network disruption rather than a simple Wi‑Fi signal problem.

Two patterns show up a lot:

  • The device connects to Wi‑Fi, but web pages never load.
  • The device reaches some local devices, but not others, or access drops in and out.

That split helps separate a gateway problem, a DNS problem, and an IP conflict from plain coverage trouble.

Manual static IP or eero reservation: which one are you actually using?

A manual static IP is set on the device itself. An eero DHCP reservation is set on the router side, so eero keeps handing that device the same address through DHCP. For most home devices, the reservation is safer because eero stays in control of the subnet and gateway details.

That difference matters. If you set a manual static IP on a laptop, printer, camera, or TV, the device has to match the current eero network exactly. If the eero LAN changes later, the old manual settings can quietly point to the wrong place. With a reservation, the device still uses DHCP, so it keeps a fixed address without you hard-coding the rest of the network settings.

In practice, eero support says you can use IP reservations for devices on the eero network, and that the eeros themselves do not need to be assigned their own IP addresses from the device side. If your goal is just to keep a device easy to find, a reservation is usually the better fit.

Before you start

Check the current eero app or support guidance before you change anything, because menus and wording can change. If the device is the only way you reach the network, keep the old settings written down so you can roll back if needed.

Use this section to separate a device-side static IP from an eero gateway/static WAN setting:

  • A manual static IP lives on the device.
  • A reservation lives on the router.
  • A static WAN setup on the gateway eero is a separate ISP-facing setup and uses the details your ISP gives you.

If you are changing the eero gateway’s WAN settings rather than a device on the LAN, eero says you need the static IP address, subnet mask, and router IP from your ISP. That is not the same as giving a printer or laptop a manual static IP on the home network.

Match the address, gateway, and DNS to the current eero subnet

A manual static IP only works when the device’s address, subnet mask, default gateway, and DNS server all fit the current eero LAN. If any one of those is wrong, the device may still connect to Wi‑Fi but lose LAN or internet access.

The most common mistake is the wrong subnet. Say your old router used one private range and eero now uses another. If the device still holds an address from the old range, it may sit outside the current LAN and stop talking to the rest of the network. The next most common mistake is the default gateway, especially after moving from a gateway router to eero. If that gateway still points to the old router, internet traffic has nowhere useful to go.

DNS can be deceptive. A DNS problem can make the internet look dead even when local traffic still works, because the device cannot translate names like example.com into an IP address. Duplicate IPs are different again: the device may work for a moment, then fail when another device grabs the same address. That often shows up as intermittent access rather than a clean outage.

If you are checking a device by hand, compare its settings to the current eero network, not an older router label or an old setup note. If you do not know the current subnet and gateway, check the eero app or the current gateway settings before changing anything.

An eero mesh Wi‑Fi router sits beside plugged-in ethernet cables on a table.

How to tell what kind of failure you have

The symptom usually tells you where to look first. Start with what still works, because that narrows the problem faster than changing random settings.

SymptomMost likely causeWhat to check first
Wi‑Fi connects, but nothing on the internet loadsWrong gateway, bad DNS, or upstream internet issueDefault gateway, DNS, then modem/ONT and eero internet status
Wi‑Fi connects, local devices still work, but the internet does notDNS issue or wrong gatewayDNS first, then gateway
Wi‑Fi connects, internet works, but printers/NAS/local shares do notWrong subnet, duplicate IP, or local firewall rulesSubnet mask, IP conflict, and whether the device is on the same LAN
Connection works, then drops at randomDuplicate IP or an address that conflicts with DHCPIP conflict, then switch to reservation
Only one device fails and others are fineBad address settings on that deviceThat device’s IP, gateway, and DNS

If the device can reach the router or eero gateway but not the internet, the problem is usually beyond the local link. Check the device’s default gateway and DNS first, then look at the modem or ONT and the eero internet status. If the device cannot reach printers or a NAS on the same network, the issue is more often the subnet, the address itself, or a conflict with another device. That distinction matters because a broken static IP can look like a bad Wi‑Fi signal when it is really an addressing problem.

If more than one device starts acting odd at the same time, stop blaming the static IP first. That pattern can point to a mesh or gateway problem instead of one bad device setting, especially if wired units seem to behave strangely or the app reports inconsistent connection details.

The safest way to fix it and keep it from coming back

The cleanest fix is to stop depending on a manual static IP unless you truly need one. Switch the device back to DHCP first, confirm that it can reach the network again, and then add a reservation if you still want the same address every time.

  1. On the device, change the network setting from manual static IP to automatic addressing, usually called DHCP.
  2. Save the change and reconnect the device to Wi‑Fi or Ethernet.
  3. Confirm that the device can reach the router, local devices, and the internet.
  4. If you want a fixed address, create a reservation for that device in the eero app instead of hard-coding the IP on the device.
  5. If the device still fails after switching to DHCP, check whether the eero LAN subnet, default gateway, or upstream modem/ONT changed recently.

If the device can reach the router but not the internet after the switch, the problem is probably not the address setting anymore. Recheck the gateway and DNS, then confirm the modem or ONT is online and the gateway eero is the active path. If the device still cannot see printers or a NAS, the issue is likely on the local LAN side: wrong subnet, duplicate address, or another router still in the path.

If the switch to DHCP fixes the device, the old setup was the problem. If it does not, look at the broader network. A recent gateway change, another router left online by mistake, or a mesh topology issue can break a setup that used to work. eero’s own offline troubleshooting starts with checking the modem or fiber ONT connection, then the gateway eero path, before deeper fixes.

When the issue is the mesh itself, not the IP, you’ll usually see more than one device misbehave. Wired units may appear to fall back to wireless, the app may report odd status, or the network may drop in ways that do not match one bad address. That is the point to check cabling, modem state, and whether another router or gateway is still in the path.

A smartphone lies next to an eero mesh Wi‑Fi router on a table.

Verify the fix

After the change, check three things in order: the device gets a normal address from the network, it can reach the router or gateway, and it can reach both the internet and local devices you care about.

If you moved the device to DHCP, the address should now come from eero instead of being manually forced on the device. If you added a reservation, the device should keep the same address across reconnects while still using DHCP. If it still drops off after that, the issue is probably not the static IP setting itself and you should return to the gateway, subnet, or topology checks above.

Conclusion

If you are still stuck, undo the manual static IP first and test the device on DHCP before you change anything else. That gives you a clean baseline and makes it much easier to tell whether the fault is the device setting, the eero LAN, or the rest of the network.

Frequently Asked Questions

Should I keep a manual static IP on a home device or switch to an eero reservation?

In most home setups, switch to an eero reservation. It gives you a stable address without forcing the device to carry the gateway, DNS, and subnet details itself. That is where many eero static IP problems start.

What if my device can reach the router but not the internet?

That usually points to a wrong default gateway, bad DNS, or an upstream internet problem rather than Wi‑Fi itself. Check the device’s gateway and DNS first, then confirm the modem or ONT and the gateway eero are online.

Why does only one device break after I set a static IP?

Because the address settings are usually wrong for that one device, not for the whole mesh. A subnet mismatch, duplicate IP, or stale gateway setting on that device can break it while everything else keeps working.

Sources