What a network actually is
A network is not a cable. It is an agreement.
Two machines joined by a wire can pass voltage back and forth, and that is all. To send anything meaningful they need to have settled a set of questions in advance: where does a message start and stop, who is it for, and how does the receiver know it arrived intact. That settlement is a protocol, and every layer of the Internet is one.
The smallest useful version has three parts. Two hosts, a link between them, and a message with an address on the front:
+-----------------------------------------------+| to: 192.0.2.30 from: 192.0.2.11 len: 1400 | <- header+-----------------------------------------------+| GET /index.html HTTP/1.1 ... | <- payload+-----------------------------------------------+The top half is the header: fixed fields, in a fixed order, for machines. The bottom half is the payload — the thing you actually wanted to send, which the network carries without reading.
Why packets, and not files
A link is shared. If one machine could hold it for the length of a whole file, everyone else would wait for the length of a whole file.
So data is cut into packets: bounded chunks, each with its own header, each routed independently. Many conversations then interleave on one wire, a chunk lost to interference is resent on its own rather than restarting the transfer, and no single sender can monopolise the link. The cost is that packets can arrive out of order, twice, or not at all — which is precisely the mess TCP exists to clean up.
Each step across a link is a hop, and each hop is a fresh decision by a fresh router that has no memory of the ones before it. Press play and follow one packet across all six:
Latency is not bandwidth
The last idea to fix before anything else makes sense: two different things are called "speed", and confusing them is behind most wrong guesses about why a page is slow.
| What it measures | Fixed by | |
|---|---|---|
| latency | How long one message takes to arrive | Being closer. Nothing else. |
| bandwidth | How much data flows per second once it starts | A fatter link |
A page load is not one big transfer; it is dozens of small round trips, each waiting on the one before it. That is why a fast connection on the other side of an ocean still feels slow, and why the fastest request is always the one that is never made.
Key takeaways
- A network is an agreement about message format and ordering — a protocol — not the wire underneath it.
- Every packet is a header for the machines in between and a payload for the machine at the end. Routers read only the first.
- Data is split into packets so one link can carry many conversations, and so a loss costs one chunk rather than one file.
- A router decides one hop at a time with no memory and no view of the whole path. The TTL counter is what makes that safe.
- Latency is a delay and bandwidth is a rate. Distance sets a floor on the first that money cannot buy through.