How Networks Work — LAN and WAN, Agreements and Small Parcels, Roads and Speed
The result first
A network is simply machines connected so that data can travel between them. Inside one house that connection is a LAN; between distant places it is a WAN. Data travels by shared agreements, split into small parcels, along a road — and how fast it feels depends on the road’s width and on the delay before an answer comes back.
I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with my AI butler Moka (Muse). Today I will walk through how computers and phones connect, and how words and pictures actually arrive — using the post and the roads as pictures anyone can follow.
Where a technical word cannot be avoided, I add a short note. Everywhere else, I use everyday words.
What a network is
A network is the whole connection that lets machines — computers, phones and the like — exchange data with each other.
A machine on its own can only do work inside itself. Once connected, it can fetch words and pictures kept on another machine, or send letter-like data to someone far away.
At home, showing a phone photo on the television, or printing a document from a computer in another room, works because the machines are connected. The connection can run along a cable or through the air by radio; in both cases, data travels along a road. The internet is this same connection grown to cover the whole world — its largest shape.
One point matters at the start: if the connection breaks partway, the other machine’s data becomes unreachable even though nothing is broken. Separating “the machine has failed” from “the connection is unwell” is the first step in this whole subject.
LAN and WAN — inside the house, and between distant places
Connections divide by size into two kinds.
The first is the LAN — in this article, the connection inside the house. At home, the computer, the phone and the printer connect around the router. The router is the sorter inside the house: it decides which machine each piece of data goes to, much like the person who sorts deliveries within a home.
The second is the WAN — the connection between distant places. A head office and a branch, a house and a far-away server: connections that leave the building and stretch far belong here. The internet itself can be seen as distant-place connections from all over the world, bundled together.
This split makes trouble easier to locate. “It prints at home but cannot be seen from outside” — trouble like that often sits exactly on the border between the inside connection and the outside one.
The inside connection is a range you set up and look after yourself. The distant connection runs along a provider’s roads, so some trouble there cannot be fixed from your house alone. Working out which range the trouble sits in is the first step toward fixing it.
Roads and speed — width, and the delay of the reply
The road data travels on is called a line. How fast things feel is decided by two properties of that road.
The first is bandwidth — here, the width of the road. The wider it is, the more data it can carry at once. Push a big load down a narrow road and a queue forms, just as a lane for one car at a time differs from a wide road with many lanes.
The second is latency — here, the delay of the reply: the wait between asking and the answer coming back. Even on a wide road, a distant partner — or many sortings along the way — makes the reply late. A wide road to a far place still takes time; a narrow road to a near place can still arrive quickly.
A fibre line carries data as signals of light; it is easy to make wide, and easy to keep the delay small. Even so, at hours when many people use the same road at once, each person’s share shrinks and things feel slow.
There is a useful way to tell the two apart. Video that keeps stopping usually means the road is not wide enough; a slow reaction after you press something usually means the delay is large. Asking “is the load too big, or is the reply late?” makes any slowness much easier to describe.
Agreements and small parcels — the post and the delivery van
Machines being connected is not enough: if the way of sending is not shared, data does not arrive correctly. That shared way of sending is called a protocol.
Note: a protocol is the set of steps and rules machines use when they send data to each other.
How to write the address, how to say “sent,” how to ask again when something did not arrive — all of that is part of the agreement. Because the agreement is shared worldwide, machines made by different companies can still connect — much as a letter’s address can be read across countries.
The other key device is splitting. Large data is not sent as it is; it is divided into small parcels called packets — here, small split parcels.
Note: a packet is one small parcel of data, split off for sending.
Each parcel carries its destination and its order number. Even if parcels take different roads on the way, they can be put back together in order at the far end. And if one parcel fails to arrive, only that one needs to be sent again — little is wasted.
It resembles a delivery service that splits a load into small boxes: rather than moving one huge load whole, the boxes can flow around the gaps in the roads, so the whole stream rarely stops. Every page that appears and every mail that arrives is, behind the scenes, this splitting and reassembly repeated over and over.
How this house’s site is connected
This house’s site is built in a “send the parts” style. The parts — the words and the pictures — are made first and sent to a storehouse (GitHub). The delivery system (Cloudflare) receives them, places them at a spot near the reader, and hands them over from there.
Handing over from near the reader shortens the road, compared with fetching everything from one far place each time, so pages show faster. It is the “keep the delay small” idea from the previous section, built into the way the site itself is made.
The making has three roles: a tool called Astro assembles the parts, GitHub stores them, and Cloudflare hands them over.
When trouble appears in this connection, the basic way to check is step by step: were the parts made, did they reach the storehouse, and are they being handed over from the nearby spot?
In short — split it up, and the shape appears
- See connections in two parts: inside the house (LAN), and between distant places (WAN)
- Speed is decided by the road’s width together with the delay of the reply
- Data travels by a shared agreement, split into small parcels, and is reassembled where it arrives
“Network” sounds like a big word, but inside it is a simple arrangement: along a road, in an agreed shape, parcels are carried. Keep the post and the roads in mind, split the problem into its parts, and even trouble becomes easier to place.
- November 21, 2026 ― English draft created (result-first rewrite of the Japanese article; based on an item that sat unpublished on the knowledge shelf).(5,589 characters)
- November 21, 2026 ― Published (all 7 languages at once, on the user's instruction on 2026-11-21 to publish the unpublished items in every language. Japanese original: ledger No. 1734.)(5,589 characters)
