Homes increasingly contain several boxes that all look like “the router”: a fiber ONT, cable modem, ISP gateway, personal router, mesh primary, mesh satellites, switches, access points, and smart-home bridges. The device providing Wi-Fi is not always the device performing routing or NAT. Before changing settings, identify the boundary device that owns the LAN default gateway and the upstream device that owns the public connection.

What you are changing?

The most reliable clue is the default gateway shown on a normal client. That address usually belongs to the layer-3 device routing the client subnet. From there, cabling and traceroute reveal whether another private router exists upstream. DHCP server information can also identify which box is assigning addresses. Do not rely on logos or physical placement alone.

A safe step-by-step workflow

  • On a connected laptop or phone, record the local IP address, prefix/subnet mask, and default gateway.
  • Open the gateway address locally and identify the manufacturer/model from the interface without entering random credentials.
  • Trace the physical cable from the router WAN port toward the modem, ONT, or ISP gateway where practical.
  • Run a traceroute to a public destination and look for multiple private-address hops before the public network, which can indicate double routing.
  • Check which device runs DHCP for the client subnet and whether mesh nodes are in router or bridge/access-point mode.
  • Draw a simple topology: ISP line → modem/ONT/gateway → router → switches/APs → clients. Label addresses only after verifying them.

Deeper technical context

A mesh system complicates identification because satellites often bridge traffic back to one primary router. Their IP addresses are management endpoints, not independent default gateways. Likewise, an ISP gateway can be placed into bridge or passthrough mode while a personal router performs NAT and DHCP. Conversely, a personal “router” may be running as a plain access point behind the ISP gateway. The job is to discover function, not just device category printed on the box.

A concrete example

A client at 192.168.50.20/24 with gateway 192.168.50.1 may be connected to an ASUS mesh. Traceroute shows 192.168.50.1 as the first hop and a public address next, while the fiber ONT has no private routed hop. That strongly suggests the ASUS primary is the router and the ONT is acting as the access device, even though both are essential to internet service.

Common mistakes that create bad conclusions

  • Assuming the Wi-Fi access point is automatically the router.
  • Opening every private IP on the subnet and guessing passwords.
  • Changing bridge mode before drawing the current topology.
  • Calling the modem, ONT, router, and mesh nodes all “gateway” and then losing track of which device owns which function.

What if the default gateway is the ISP gateway?

Then that device is probably routing your client subnet unless another device is using proxy/bridge arrangements. Check mode and traceroute.

Can a switch be the default gateway?

A basic layer-2 switch cannot, but a managed layer-3 switch can route. Home networks usually use the router/gateway for this role.

Does every mesh node have a gateway IP?

Nodes have management addresses, but clients normally share the gateway provided by the primary router or upstream router.

Why identify the router before troubleshooting?

Because port forwarding, DHCP, firewall, DNS, VPN, and bridge settings must be changed on the device that actually performs those functions.