FieldnotesPractical technology

Field guide / Home networking

Make sense of your home network

Before restarting everything, separate the local connection from the connection to the outside world. A simple map makes troubleshooting much less mysterious.

Beginner notes · No special tools required to get started

1. Name the pieces

Your home network connects your devices to one another. Your internet connection links that network to other networks. They overlap in everyday use, but they are not the same thing.

  • A router moves traffic between networks. In a typical home it connects your local network to your provider and acts as the default gateway for your devices.
  • A wireless access point connects devices over Wi-Fi. It is often built into the router, though separate access points can extend coverage.
  • A switch connects wired devices on the local network. The extra Ethernet sockets on a home router often perform this job.
  • A modem or optical terminal connects to the provider’s cable, telephone, or fibre service. It may be separate from the router or combined with it.

One box can perform several jobs. Sketch the physical boxes and cables in your home rather than expecting a separate box for every term.

2. Understand addresses and names

A device needs an address to communicate on an IP network. Home routers commonly provide local addresses automatically using DHCP. The device also learns where its gateway is and which DNS service to use.

DNS translates a name, such as a website’s domain, into address information. If name lookup fails, a working network can still feel broken. If only one website fails, though, that does not prove DNS is the cause: the website itself may be unavailable.

Local addresses are not permanent labels for people or devices. They can change when a device reconnects. For a beginner’s network map, record a device name, its connection type, and its location before worrying about every address.

A useful distinction: seeing the Wi-Fi symbol means your device has a wireless connection. It does not, by itself, prove that your provider or the website you want is reachable.

3. Narrow the problem before changing things

  1. Define the scope. Try a second website and a second device. If one site fails everywhere, investigate that site before changing the router. If one device fails, start with that device.
  2. Check the local link. Confirm the expected network name, check that airplane mode is off, and inspect cables without disconnecting unfamiliar equipment. A loose cable can resemble a much larger outage.
  3. Compare wired and wireless. If available, use a known-working Ethernet connection to the home router. If wired access works but nearby Wi-Fi does not, the wireless part deserves attention.
  4. Check the upstream connection. Look at the provider connection indicator and interpret it using the device documentation. Indicator colours are not universal.
  5. Record and retest. Write down what failed, what still worked, and what you changed. Repeat the original test after each change.

Do not factory-reset a router as an early troubleshooting step. A reset can erase the settings needed to reconnect. If a restart is appropriate, warn other users first and follow the device’s instructions; briefly losing service may interrupt calls or transfers.

4. Improve the link you actually use

For wireless coverage, try moving the access point into a more open position before buying new equipment. Thick walls, metal cupboards, distance, and nearby radio activity can affect a connection. Test from the places where you normally work, not only beside the router.

Where both are available, 2.4 GHz often reaches farther, while 5 GHz can offer more capacity at shorter range. Neither is always faster in practice. Compare the same task in the same place and keep the result that is more consistent.

A cable is worth considering for a stationary computer or other device that needs a steady link. Route it safely, without creating a trip hazard or pinching it under a door.

5. Leave yourself a useful record

  • Label the router, provider equipment, and important cables.
  • Note the normal status indicators and the date of any change.
  • Keep setup instructions and recovery information somewhere you can access during an outage.
  • Store passwords privately, not on a diagram you share publicly.

The goal is not to memorise every networking term. It is to know enough about the path to ask a smaller question: is this the device, the local link, the provider connection, or the destination?