The box from your internet provider sits in a corner with a row of blinking lights, and most people never think about what it does beyond giving them Wi-Fi. A router is quietly doing several distinct jobs at once, moving traffic between your home and the wider internet, sharing one public address among many devices, handing out local addresses automatically, and blocking connections nobody asked for. Seeing these jobs as separate tasks, rather than as one mysterious appliance, makes home networking far easier to reason about on the day something stops working and you need to guess where the fault sits.
Routing between two networks
At its core a router does exactly what the name suggests: it routes, deciding where each packet of data should go next. Your home is one small network and the internet is a vast collection of others, and the router sits on the boundary between them. When a device sends data meant for a website, the router recognises that the destination lies outside your home and forwards it toward your provider, then passes the reply back to the device that was waiting for it.
This boundary role is why the router is called the default gateway. Every device is told to hand anything it cannot deliver locally to the router, which then works out the path onward. Under heavy load a router can let its queues swell and add lag, a fault the guide on how to tame bufferbloat addresses, but its everyday job is simply steering traffic between inside and outside.
What NAT hides and why
Your provider usually gives your home a single public address, yet you may have a dozen devices online at once. Network address translation, or NAT, is the trick that makes this work. The router keeps a table matching each internal device and its request to that shared public address, so replies coming back can be directed to the device that actually asked. It was invented mainly to conserve the limited supply of public addresses.
A side effect is that outside machines see only the router’s public address, never the private addresses of the devices behind it, which are drawn from ranges reserved for internal use. The distinction between the two kinds the guide on public and private IP addresses lays out is central to how NAT operates, and the hiding it provides is a handy consequence rather than its original purpose.
DHCP hands out local addresses
For devices to talk on your home network, each one needs a local address, and typing one into every phone, laptop and television by hand would be tedious and easy to get wrong. DHCP, the dynamic host configuration protocol, automates it. When a device joins, it asks for an address, and the router leases it one from a pool for a set time, along with the details it needs such as the gateway and the DNS server to use.
Because these addresses are handed out on a lease and can change, they are dynamic by default, though a router can reserve a fixed one for a particular device. The difference between an address that shifts and one that stays put, which the guide on static and dynamic IP addresses explains, decides whether things like a home server or a network printer keep the same address between restarts.
| Job | In plain terms | What you would notice if it stopped |
|---|---|---|
| Routing | Steers traffic between home and internet | No websites load at all |
| NAT | Shares one public address among devices | Only one device could connect |
| DHCP | Assigns local addresses automatically | Devices join only if set by hand |
| Firewall | Blocks unrequested inbound traffic | Internal devices exposed to the internet |
The firewall that comes built in
A home router also acts as a basic firewall, and NAT gives it a head start. Because incoming connections have no entry in the translation table unless a device inside asked for them, unrequested traffic from the internet has nowhere to go and is dropped. Most routers add a stateful firewall on top of that, tracking which conversations your devices started and allowing only the matching replies back through.
This turns away a great deal of unsolicited probing, but it is not a complete shield. It does little about threats you invite in, such as a malicious download or a link in an email, and features like port forwarding deliberately open a path through it. The firewall guards the front door against uninvited callers; it does not vet the visitors your own devices choose to let in.
The modem and router split
A router is often confused with the modem, but the two do separate jobs. The modem translates between your provider’s signal, whether that arrives over a phone line, coaxial cable or fibre, and the standard Ethernet your equipment understands. The router then takes that single connection and shares it among your devices, adding the NAT, DHCP and firewall duties. The modem gets you to the internet; the router builds and manages your home network.
Many providers supply a combined unit that does both in one box, which is why the roles blur together. Most such boxes also include a wireless access point, the part that handles the wireless generations the guide on comparing the Wi-Fi standards describes, so a single device may be modem, router and access point all at once. Knowing the functions are distinct helps a great deal when you want to replace only one of them.
Putting the pieces together
A router is not one gadget doing a single thing but a small bundle of cooperating jobs. It routes traffic between your home and the internet, uses NAT to let many devices share one public address, runs DHCP so those devices receive local addresses without fuss, and applies a firewall that turns away traffic nobody requested. Each job is simple on its own, and seeing them apart removes most of the mystery from the box.
When home networking goes wrong, the fault usually belongs to one of these functions rather than the whole unit. A device with no address points at DHCP, a service that will not accept incoming connections points at NAT or the firewall, and a connection that crawls under load points at how the router handles its queues. Naming the parts is the first real step toward fixing them.
Frequently asked questions
What does a router actually do?
A router connects your home network to the internet and manages the traffic between the two. It routes data to the right destination, uses NAT so many devices can share one public address, runs DHCP to give each device a local address automatically, and provides a firewall that blocks unrequested incoming connections. In most homes it also contains the Wi-Fi access point your devices connect to wirelessly.
Is a modem the same as a router?
No, though they are frequently combined in one box. A modem translates your provider’s signal, arriving over cable, phone line or fibre, into standard Ethernet. A router then shares that single connection among your devices and handles NAT, DHCP and the firewall. The modem gets you onto the internet, while the router builds your local network. Many provider-supplied units perform both jobs, which is why people mix the terms up.
What is NAT?
NAT, network address translation, lets many devices share the single public address your provider assigns. The router keeps a table linking each internal device’s requests to that shared address, so replies return to the device that asked. It was created to conserve limited public addresses, and as a side effect it hides your internal devices from the outside, since they use private addresses that are not visible out on the internet.
