Packet Path/

What Is a Network, Really?

Enterprise Network Engineer · Module 1: Networking Fundamentals

Lesson 1 of 8

Foundations⏱ 25 min

Prerequisites: none — start here

What you'll be able to do: define what a network is, tell a LAN from a WAN from the internet, and name who owns and runs each one.

Picture your street with no postal service. A birthday card for your neighbor means walking it over yourself. A letter across town means driving it there. A package to another city means finding someone with a truck — and nobody agrees on envelopes, addresses, or delivery days.

A computer network is the postal system for messages between computers. When your laptop asks another computer for a photo, something must carry that request there and bring the answer back — addressed correctly, no matter how many computers sit in between.

The twist: nobody built this system top-down. Your home setup, a company's offices, and the giant web tying them together are owned by different people, built for different reasons — yet your message crosses all of them without asking permission.

So who is in charge? Who do you call when it breaks?

Here's the puzzle.

Scenario. Your friend Maya is setting up internet for her grandmother and announces she's figured it all out: "The internet is one giant computer in California. Your phone just connects to it." She's about to call the wrong company about a problem she doesn't understand yet — and her grandmother's office manager is making the same mistake at work. Three short exhibits below describe three real networks. Sort them out before Maya dials.

Given artifacts. Read all three exhibits, then look at the diagram (hover any shape for a reminder of what it shows).

Exhibit A — Maya's apartment

Four devices — a phone, a laptop, a TV, and a game console — all connect through a single box rented from the company that sold Maya her internet plan. Everything sits inside one apartment. Nothing here is reachable from the outside world. </details>

Exhibit B — Grandmother's employer

Twelve offices in five cities. Each office has a setup like Exhibit A, and the company pays a carrier for private connections linking all twelve offices together, so employees share files and printers across cities. The public cannot use these connections — they belong to the company. </details>

Exhibit C — The internet company

The company Maya pays each month owns cables under streets across the state, connects hundreds of thousands of homes and businesses, and pays several other similar companies so its customers can reach computers on their networks too. </details>

Exhibit A — Maya's apartment: 4 devices, one rented box, one building 🏠 Exhibit A: one home Exhibit B — 12 offices in 5 cities, joined by private company-paid links Exhibit B: 12 offices Exhibit C — the internet company: cables across the state, pays other companies to reach further ☁️ Exhibit C: internet co. → →

Your task: for each exhibit, (1) classify it as a LAN, a WAN, or the internet itself, and (2) in one sentence per exhibit, name who owns and operates it.

Workspace: analyze-and-answer — three short text fields, one per exhibit, in the shape "Exhibit A is a ___ owned and run by ___." There is no grading; your words are just a commitment to a guess.

Hint 1 — where to look Look at size and audience in each exhibit. One serves a single home, one serves a single company's offices across cities, one sells connections to strangers by the hundred thousand. The classification follows the size.
Hint 2 — what to compare Compare who pays for each network and who is allowed on it. Exhibit B is paid for by one company for its own people — how is that different from Exhibit C, which sells access to anyone willing to pay?
Hint 3 — the mechanism The internet isn't a place or a machine — it's what emerges when many independent networks agree to hand messages to each other. Ask of each exhibit: does this one own wires, or is it the cooperation itself? One of your three classifications is probably wrong — take a hard second look at whichever one felt most like "the internet."

Commitment ritual: below the workspace sits a checkbox — "I've attempted this challenge and thought it through." Checking it (with or without typing an answer) reveals the worked answer in S7. Nothing is graded; the checkbox is a promise to yourself that you struggled first. (Honor system for now — real progress tracking arrives with accounts.)

Checking the box reveals the worked answer in S7 below. Returning learners stay unlocked.

A network is just devices that can reach each other

A network (two or more devices connected so they can exchange messages) is simpler than the word sounds. Two laptops sharing files across a desk are a network. So are a billion phones — just a much bigger one. The definition never mentions size, speed, or wires: if devices can exchange messages, they form a network.

Each device on it is a node (any single device connected to a network — your phone, a laptop, a printer, a game console). And whatever carries the messages between nodes is a link (a cable, or a wireless signal — the road the messages travel on). Nodes plus links: that's the whole recipe. Everything else in networking is elaboration on those two ingredients.

Why do networks exist at all? Three reasons, and they haven't changed in fifty years: to share expensive things (one printer for the whole family instead of four), to communicate (messages between people), and to reach things that live elsewhere (a photo stored on someone else's computer).

Why this matters for the challenge: every exhibit is built from nodes and links. The puzzle is never "is this a network?" — it's always how big and whose.

LAN: your building, your rules

A LAN (local area network — a network covering one small area, like a home, a classroom, or a single office, run by whoever lives or works there) is the smallest interesting network. One place, one owner, one set of rules. Your home wifi is a LAN. So is the network in a coffee shop. The defining traits are small and single-owner: the person who pays for it decides who may join.

Because it's small and privately owned, a LAN is fast to fix and easy to reason about — when it breaks, you know exactly whose problem it is.

Why this matters for the challenge: one exhibit describes a single building under one household. Size plus ownership gives it away.

WAN: many places, one organization — or one seller

A WAN (wide area network — a network joining far-apart places, built and run by an organization for its own use or by a company that sells connections) is what you get when one LAN isn't enough. It comes in two flavors that beginners constantly mix up.

Flavor one: a private WAN — a single company pays to connect its own distant offices so they work like one network. Nobody else is invited. Flavor two: a carrier's WAN — a company builds long-distance links and sells access to them; this is the business Maya's internet company is in. Same technology, opposite audiences: one serves its owner, the other serves paying strangers.

Why this matters for the challenge: two exhibits describe far-apart places joined together — but their audiences (one company vs. paying strangers) put them in different flavors of the same category.

The internet: networks agreeing to share

The internet (the global collection of independent networks that agree to pass messages to each other) is not a network in the way the others are — it's networks of networks. No one built it, no one owns it, and no one can switch it off, because "it" is really thousands of owners cooperating: your internet company hands your message to another company, which hands it to another, until it arrives.

This is why Maya's "giant computer in California" idea fails on every count. A single computer would have a single owner, a single location, and a single off switch. The internet has thousands of owners, spans every continent, and survives any one of them disappearing — because the agreement to cooperate doesn't live in any one machine.

Why this matters for the challenge: if an exhibit owns wires, bills customers, and has competitors, it's a participant in the internet — not the internet itself.

Clients ask, servers answer

Inside any network, devices take roles. A client (a device that asks for something — your phone requesting a video) asks; a server (a computer whose job is answering many clients — the machine that sends the video back) answers; and the useful thing delivered is a service (video streaming, file sharing, messaging — the reason anyone bothered connecting). Your laptop is a client when it loads a page and could be a server if it shared its files — roles describe the moment, not the machine.

Why this matters for the challenge: Exhibit C's entire business is selling a service (internet access) to clients. Spotting the client/server pattern tells you who the operator is — and operators own networks.

🏠 Maya's home (a LAN) ☁️ the internet: networks cooperating company offices (a WAN) ● request ● reply
  1. Step 1 of 5: Maya's laptop has a message for a computer in her grandmother's office — it starts on her home LAN.
  2. Step 2 of 5: The message leaves the LAN through the rented box and enters her internet company's network (blue dot traveling right).
  3. Step 3 of 5: Crossing the cloud, the message is handed between several independent companies' networks — that cooperation is the internet. No single "big computer" appears.
  4. Step 4 of 5: The message arrives at the company's private WAN and is delivered to the office computer.
  5. Step 5 of 5: The reply (green dot) retraces the path home. Every handoff is one network trusting the next — ownership changes at every border.
🔒 The worked answer is hidden until you commit...

Check yourself — nothing here is graded. Wrong answers are the useful ones; each explains why.

Question 1. Which of these is a LAN?

Question 2. Who owns the internet?

Question 3. Your home wifi dies, but your neighbor's works fine and your phone's mobile data works too. What's the smartest first move?

Question 4. You tap a video on your phone and it plays. In that moment, your phone is the…

Question 5. A bakery with two shops across town wants the cash registers in both shops to share one inventory file, privately — not over the open internet. What do they need?

Next: How Computers Talk: Packets, Frames, and Addresses — you now know what networks are; next you'll open one up and see how the messages inside actually travel, wrapped in layers like a letter in an envelope in a courier's pouch.