Advertisement

ASUS router loses internet after modem restart: fix WAN

If your ASUS router still has Wi‑Fi but the internet drops right after a modem restart, the WAN side is usually stuck on an old lease, MAC binding, or link negotiation issue. This article walks you through the checks that show where the handoff failed and how to get it back.

Networking 8 min read
An ASUS Wi‑Fi router sits on a desk next to a modem.

If your ASUS router still shows Wi‑Fi after a modem restart but the internet is gone, the WAN side has usually failed to recover cleanly. The most common causes are a stale WAN lease, the modem holding the old session, MAC binding, or a WAN link negotiation problem. Start by checking the ASUS WAN status page, then power-cycle the modem and router in the correct order so the router gets a fresh handoff.

What this symptom usually means

The Wi‑Fi can stay up even when the upstream connection is broken. That is why phones and laptops still see the ASUS network, but nothing reaches the internet.

In practice, this usually starts after the modem reboots and does not give the router a fresh connection cleanly. The ASUS router may keep an old WAN state, the modem may still be tied to the previous session or MAC address, or the WAN port may come back with a link that looks alive but never finishes negotiating properly.

A short reboot often is not enough to clear that state. If the modem only lost power for a moment, it may still remember the old session and refuse to hand service back the way you expect.

Before you start

Use the router's web admin page, not just the mobile app, so you can see the WAN status directly.

  • Leave the modem and ASUS router alone until you have checked the WAN page once.
  • If your modem is also a gateway device, note that it can behave differently from a bridged modem after a restart; gateway mode keeps more session state inside the modem, while bridge mode is usually simpler for the ASUS router to recover from.
  • If the modem is part of your ISP service, do not factory reset it unless your ISP told you to.
  • If you change one ASUS setting, change only one at a time so you can tell what fixed it.

Check the ASUS WAN status page first

Open the ASUS web interface and look at the WAN status page before you change any settings. You are trying to separate the fault into one of two cases: the router never got a WAN address, or it got one but still cannot pass traffic.

Use this quick check:

What you see on the WAN pageWhat it usually means
No WAN IP, no gateway, or a self-assigned addressThe router did not get a proper lease from the modem or ISP side
WAN IP and gateway are present, but websites still failThe WAN address exists, but traffic is failing after that point
The WAN port never comes up or keeps flappingThe physical link, modem handoff, or speed negotiation is failing

If you see no WAN IP, focus on lease renewal and modem handoff. If you see a WAN IP but no working internet, focus on DNS, MAC binding, the modem's session state, and link speed.

The clean power-cycle order that usually restores service

Use a full power cycle, not a quick off-and-on restart. The modem needs to come fully back online before the ASUS router asks for a new WAN lease.

  1. Unplug both the modem and the ASUS router.
  2. Leave them off long enough for the modem to clear its old session state.
  3. Plug in the modem first and wait until it is fully online.
  4. Once the modem is ready, plug in the ASUS router and let it boot normally.
  5. Recheck the ASUS WAN status page after the router finishes reconnecting.

If the WAN page now shows a valid address and the internet works, the issue was the handoff timing. If the problem comes back only when the modem has restarted, the modem is likely not releasing its old state cleanly.

An ASUS router and a modem sit unplugged on a floor or table.

If the router has a WAN IP but still no internet

When the WAN page shows an address but nothing loads, the router is connected far enough to look normal, but something in the handoff is still wrong. Make one change at a time and stop if a change makes the connection worse.

  1. Check whether the modem is a gateway or a bridged modem.

If it is a gateway, it may keep session memory and expect the same device identity after a restart. If it is bridged, the ASUS router should usually be the device that gets the public-facing connection, which makes recovery more straightforward.

  1. Try WAN DHCP first on the ASUS side.

Make sure the WAN connection type is set to DHCP or automatic if that is what your ISP uses. If the router is waiting for the wrong WAN mode, it can look connected without actually renewing the lease.

  1. Try MAC clone only if the WAN IP is present but traffic still fails.

MAC cloning can help when the modem or ISP side is binding service to the last device it saw. Use the MAC of the device that previously worked, or the ISP-required identity if you have one.

  1. Put DNS back to automatic unless you already use a known-good DNS setup.

If IP addresses work but site names do not, the router may be reaching the internet while name resolution is failing. Switching DNS back to automatic is the safest first test.

  1. Check the WAN link speed setting only if the link still will not stabilize.

If the port keeps renegotiating, leave the speed setting on Auto first. Only change it if your modem or ISP documentation says a specific rate is required. A speed mismatch can look like a dead internet connection even though the cable is seated correctly.

If you are using a modem in gateway mode, it may take longer to forget the old router session. In that case, a proper full power-off is usually more effective than repeating soft reboots.

How to confirm the fix

The fix is real when the ASUS WAN page shows a valid WAN IP, gateway, and DNS, and the connection stays up after both devices are restarted.

  1. Confirm that the WAN page now shows a valid address and gateway.
  2. Open a website from a wired device, then from a wireless device, so you know the router is passing traffic normally on both sides.
  3. Reboot the modem and ASUS router again in the same modem-first order.
  4. Check that the ASUS router reconnects on its own without needing extra changes.

If the connection survives another restart, the handoff is stable. If it only fails again after the modem has been off long enough to forget its state, the problem is still in lease renewal, MAC binding, or modem session recovery rather than Wi‑Fi itself.

When the problem is not on the ASUS side

If the ASUS router never gets a WAN IP after a clean modem-first restart, the modem may not be handing off service properly. If the modem says it is online but nothing passes through it, the issue may be the ISP line, the modem itself, or bad modem firmware state.

That is the point where more ASUS setting changes usually stop helping. If the WAN page stays empty after a clean reboot sequence, or the modem keeps dropping before the router can renew, contact the ISP and ask them to check the line and the modem state. If the modem is provided by the ISP, they may need to replace it or push a firmware fix.

An ASUS router and a modem are placed together on a shelf near a wall outlet.

Frequently Asked Questions

How do I tell whether it is the modem or the ASUS router?

Check the ASUS WAN status page first. If there is no WAN IP or gateway after a clean modem-first reboot, the handoff is failing. If the WAN IP is present but nothing reaches the internet, the modem, DNS, MAC binding, or link negotiation is more likely than the Wi‑Fi side.

Should the modem be in bridge mode or gateway mode?

If your ISP and modem support bridge mode, it usually makes this kind of restart problem easier to diagnose because the ASUS router becomes the main WAN device. In gateway mode, the modem keeps more of the session state, so restart problems are more common. If your service depends on a specific mode, follow the ISP's setup.

Do I need to factory reset the ASUS router?

Usually not. If the problem starts after a modem restart, a factory reset is more drastic than you need. Start with the WAN page, the correct power-cycle order, then DHCP, MAC clone, DNS, and WAN speed checks before you think about a reset.