E-Learning Platform
0 of 139 builtAlways freeSign in
← Network Foundations I
1.04

Packets

On this stop
  • Packets
  • Reassembly

You've bought a piano, and it has to cross the country. Nobody ships a piano in one piece down one road and hopes. It gets dismantled, packed into numbered crates — 3 of 14 — each crate labeled with the destination address, and if the crates arrive on different trucks on different days, fine: the movers reassemble by the numbers. Networks looked at that and said: that's how we'll send everything. Including, frankly, things much heavier than pianos.

The packet

A packet is one crate of a message: a small chunk of the bits, plus a label. The label carries, among other things, where it's going, where it came from, and which piece of the whole it is — the "3 of 14". Your photo doesn't leave your phone as one long stream; it leaves as hundreds of packets, each a self-contained, addressed, numbered parcel. A movie is millions of them. Even the tiniest message gets the treatment.

Why go to the trouble? Because tiny, independent parcels buy the network three enormous wins:

  • Sharing. Networks are shared roads. If one device could send a movie as a single unbroken transmission, everyone else would wait behind it like cars behind a parade. Small packets mean everyone's parcels interleave — yours, your sister's, the neighbor's — and the road serves all of them at once.
  • Independence. Each packet carries a full address, so each can travel on its own. Two crates of one piano may ride different trucks; two packets of one photo may take different paths and arrive out of order. Nobody minds, because —
  • Cheap repair. If something goes wrong, it goes wrong to a crate, not the piano. Losing packet 7 of 200 means re-sending packet 7. Not the photo. This is the win that makes the other two safe to enjoy.

Reassembly: the far end's quiet work

The receiving device is the moving crew. As packets arrive — out of order, in bursts, mixed in with parcels from three other conversations — it sorts them by their numbers and rebuilds the original bits exactly. Packet 9 before packet 8? Reordered, no drama. And when a number never shows up, the receiver does the politely relentless thing: it asks the sender for that piece again. Ask, receive, slot it in. Between numbering, reordering, and re-asking, the network can be having a genuinely scrappy day underneath while what you see is one flawless photo. (The system that runs this ask-again bookkeeping has a name and a fan club; a later course can introduce you. The idea is what belongs to this one.)

Here's the mental upgrade to keep: when a page is slow, you're not watching "the internet" fail as one thing. You're watching parcels — a few of them late, a few re-asked-for. The freeze at second 47 of a video is a missing crate being fetched again. It usually succeeds, which is why it's a stutter and not an ending.

One thing packets quietly assume, though: that address on every label. Who hands out addresses? What do they look like? That's Unit 2's whole territory. First, two more stops in the home — next lesson, the device that reads those labels inside your own four walls and hands each parcel to exactly the right machine.