A router connects IP networks and forwards packets between them. When a packet arrives, the router examines its destination address, compares that address with entries in a forwarding table, and sends the packet through the selected interface toward its next hop. A home router usually combines that routing job with Ethernet switching, Wi-Fi, address assignment, firewall functions, and often network address translation.
What happens in five steps
1. A device receives network configuration
When a phone or computer joins a home network, it obtains information such as its local IP address, network prefix, default router, and DNS resolver. IPv4 networks commonly provide these values through DHCP. IPv6 can use router advertisements, DHCPv6, or both. This configuration tells the device which destinations are local and where to send traffic destined elsewhere. The settings may be temporary and can be renewed while the device remains connected.
2. The device creates a packet
An application passes data to the operating system, which places it into an IP packet containing source and destination addresses. If the destination is outside the local network, the device puts the packet inside a local Ethernet or Wi-Fi frame addressed to its default router. The router does not need to understand the page, video, or message merely to forward it. Local framing changes from one network segment to another while the IP destination identifies the intended endpoint.
3. The router examines the destination
The router removes the incoming link-layer framing and checks the IP header. It compares the destination address with its forwarding table, normally choosing the most specific matching network prefix. The selected entry identifies an outgoing interface, a next-hop router, or a directly connected destination. If no usable route exists, the packet cannot continue normally. The router also updates fields designed to prevent packets from circulating forever.
4. Policy and address translation may apply
A home router may check a stateful firewall policy and translate private IPv4 addresses and ports to a public address using NAT. Translation is common but is not the definition of routing, and IPv6 can be routed without traditional IPv4 NAT. The router then builds new link-layer framing suitable for the outgoing connection and transmits the packet. A denied, malformed, expired, or unrouteable packet may instead be discarded.
5. Other routers continue the journey
Each router along the path makes its own forwarding decision. The destination sends reply packets using routes that may not be identical in reverse. If the home router created an IPv4 NAT mapping, it uses that stored state to deliver the response to the correct local device. No single household router knows or controls the entire internet path, and an upstream change can alter the route without changing local Wi-Fi settings.
What a routing table contains
A forwarding table associates address prefixes with next hops and interfaces. It can include directly connected networks, a default route toward the internet provider, manually configured routes, and routes learned through protocols. Large internet routers exchange reachability information, while a typical home router relies mainly on local routes and a provider-facing default. Selecting the longest matching prefix lets a specific route override a more general one.
Router, modem, switch, and access point are different roles
A modem or network terminal connects to the provider’s delivery technology. A switch moves local frames within one network, and a wireless access point provides the radio link explained in how Wi-Fi works. A consumer gateway may place all these roles in one enclosure, but their functions remain logically distinct. This distinction helps isolate whether a fault is local radio, local routing, or provider access.
Why DHCP, DNS, and NAT appear in router settings
Home gateways commonly run a DHCP server, relay or proxy DNS requests, and perform IPv4 NAT. DHCP supplies configuration; DNS translates names into addresses; NAT rewrites address or port information. These services help operate a home network, but a router can forward packets without being the authoritative DNS server or performing NAT. Changing one function can solve one symptom while leaving another layer untouched.
Why Wi-Fi can work while the internet does not
A device can maintain a healthy radio link to the local router even when the provider connection, DNS service, upstream route, or account has failed. That separation explains why a phone can report connected without internet. The Wi-Fi symbol confirms a local link, not successful delivery to every remote service. Testing the router’s administration page can help distinguish local reachability from internet reachability.
What limits router performance
Throughput can be limited by the provider plan, radio interference, weak signal, Ethernet speed, processor capacity, firewall inspection, overloaded queues, or the remote service. Latency can rise when traffic fills a slow link. Buying a router with a high advertised wireless rate cannot make an upstream connection exceed its own capacity. Real application performance also includes retransmissions, server response, and congestion beyond the home.
Why restarting sometimes helps
A restart clears volatile state, renegotiates provider or radio connections, and reloads software. That can recover from a temporary fault, but it does not repair damaged cabling, congestion, poor placement, an outage, or outdated firmware. Repeated need for restarts is evidence to diagnose rather than a normal networking requirement. Record which lights, devices, and services failed before restarting when troubleshooting recurring problems.
A router security boundary
Change default administrator credentials, use current supported firmware, enable strong Wi-Fi encryption, disable unnecessary remote administration, and review connected devices. NAT alone is not a complete security strategy. Firewall rules, secure device configuration, updates, and protected management access each address different risks. Do not expose an administration interface to the internet unless there is a specific, secured, and maintained reason.
The useful mental model
A router is a road junction for packets. It reads the destination, consults a signpost table, applies configured policy, and sends each packet to the next segment. Services such as Wi-Fi, DHCP, NAT, DNS relay, and filtering often share the box but perform separate jobs. Understanding those boundaries makes both network design and troubleshooting more precise.
