Home Network Basics: Router, Wi-Fi, Ethernet, DHCP, DNS, and NAT Explained Together

Router

A router moves packets between networks. In a home it commonly also acts as a DHCP server, firewall, NAT gateway, Wi-Fi access point, and DNS forwarder. Those jobs can be performed by separate devices, but consumer hardware often combines them.

Wi-Fi and Ethernet

Wi-Fi and Ethernet are ways devices attach to the local network. Ethernet is normally predictable and low-latency when cabling is practical. Wi-Fi trades some of that predictability for mobility. A weak wireless connection can make the internet appear slow even when the ISP connection itself is healthy.

DHCP

DHCP automatically gives devices local IP settings. A typical lease includes an IP address, subnet mask/prefix, default gateway, and DNS server information. DHCP is why you can join a home Wi-Fi network without manually assigning an address to every phone.

Default gateway

The gateway is where a device sends traffic destined for somewhere outside its own local subnet. On most home networks, the default gateway is the router. That same address is often where the local administration page lives.

DNS

DNS translates names into records computers can use. When you visit a website, your device or router asks a resolver for the relevant address. Changing DNS can affect lookup behavior, but it does not magically increase the raw speed of the physical internet connection.

NAT

IPv4 home networks commonly use Network Address Translation so many private local devices can share one public IPv4 connection. NAT is a translation function, not a substitute for a firewall, although consumer routers usually implement both together.

Modem, ONT, and gateway

Cable and DSL connections may use a modem. Fiber commonly uses an optical network terminal (ONT). An ISP “gateway” often combines modem/ONT-facing functions with routing and Wi-Fi. If you add your own router behind an ISP gateway without changing modes, you can end up with double NAT.

A useful troubleshooting order

1. Check whether the device is connected to Wi-Fi or Ethernet.
2. Check whether it received a local IP and gateway.
3. Check whether the router can reach the ISP.
4. Check DNS if numeric IP connectivity works but names do not.
5. Only then change more advanced router settings.

This sequence separates local wireless problems from router, ISP, and DNS problems instead of resetting everything at once.

Walk through one web request

Your device gets configuration from DHCP, resolves the site name through DNS, decides the destination is outside the local subnet, sends the packet to the gateway, the router forwards/NATs it toward the ISP, and the response returns. Wi-Fi/Ethernet only describe the local link used to reach the gateway.

Why this model speeds up troubleshooting?

“No internet” can now be split: no link, no IP lease, no gateway, no WAN route, DNS failure, or remote-site/application failure. Each layer has different evidence and fixes.

Map your own network

Draw modem/ONT, router, switches, mesh/access points and major devices. Label which box runs DHCP/NAT and note the LAN subnet. That simple diagram prevents many double-router and reset mistakes.