LANs, WANs and Every Network Between

LANs, WANs and Every Network Between

What you'll learn

• Apply the two-question test — who owns it? and how far does it reach? — to tell a LAN from a WAN
• Place CAN, MAN, PAN and WLAN correctly on the size ladder
• Explain what the Internet actually is: a mesh of WAN links between providers, not a single thing
• Mark the LAN boundary and the WAN link on a diagram of your own home network

This lesson continues Chapter 1 of Network Essentials, which draws a distinction the whole rest of the course leans on. The book's framing is wonderfully practical: the difference between the network types is less about geography than about ownership. You own your LAN; you rent your WAN. Keep that sentence in mind — it resolves almost every classification puzzle in this lesson.

The LAN: your network, your rules

A Local Area Network (LAN) is a network confined to a single location — a home, an office, one floor of a building, a school lab — where the organization (or household) owns every piece of it. You bought the router. You ran the cables, or at least you could touch them if you wanted to. If something needs changing, you change it; if something breaks, it is your problem and your privilege to fix.

That ownership has consequences you will appreciate throughout the course. On your LAN you decide the equipment, the layout, the security rules, and the speed — modern LAN connections are fast precisely because short, private, fully-owned links are cheap to make fast. Every device you inventoried in Lesson 1 lives on your LAN.

The WAN: renting the road

Now suppose your company has an office in one city and a second office three hundred kilometers away, and the two need to behave like one network. You cannot dig a three-hundred-kilometer trench, negotiate with every landowner along the way, and lay your own cable — no ordinary organization can. Instead you pay someone whose entire business is long-distance connections: a telecommunications provider.

A Wide Area Network (WAN) connects locations that are far apart, over links you rent from a service provider. You own the equipment at each end; the provider owns the long middle. That is the book's enduring picture of a WAN link: a rented connection. Your home has one too — the line from your router to your Internet provider is a small but genuine WAN link. You pay for it every month, which is a good reminder of who owns it.

The two-question test now works on anything. Single location, all equipment yours? LAN. Distant locations joined by links you pay a provider for? WAN.

Why not one giant network?

Here is a question the book poses on the way to explaining routers: why have separate networks at all? Why not connect everything into one enormous shared network?

Because a shared medium has physical limits. Only so many signals can coexist on a wire or in a radio channel before they crowd each other out. In Lesson 1 you saw that a network is one big broadcast domain — a space where an announcement reaches everyone. The more devices share that space, the more announcements, until the useful conversations drown. Run the thought experiment at full scale: if the entire Internet were one broadcast domain, billions of devices would hear billions of announcements, and nothing would get through at all. A network that congested no longer deserves the name.

So big networks must be split into many separate, manageably sized ones — and then something must carry data between them without merging them back into one shared space. That something is a router: a device that blocks broadcasts at the border of each network but forwards data that is addressed to another network. A classic analogy from Dr. Al-Doori's course: you leave for work, hear on the radio that an accident has jammed your usual road, and immediately start weighing alternate routes. A router does this for a living — it knows the possible paths toward a destination network and chooses the best one available. Two behaviors distinguish it from the switch you met in Lesson 1: a router does not flood when in doubt (if it has no route to a destination, it drops the data), and it deliberately refuses to pass broadcasts. Routers get their full treatment in Modules 3 and 5; here they matter because they are the doorways between all the network types in this lesson.

So what is the Internet?

With LANs, WANs and routers in hand, the Internet stops being a vague cloud. The Internet is not one network, not a place, and has no center and no owner. It is a mesh of WAN links between providers — thousands of independent networks (ISPs and the big carriers) that agreed to interconnect with one another, with routers making the hop-by-hop decisions that carry your data from your LAN, through your provider, across other providers' networks, to a LAN on the far side of the world. The name says it plainly: an inter-network, a network of networks. Your LAN attaches to this mesh at exactly one point — the WAN link you rent — which is why finding that point on your own diagram (in this lesson's activity) is worth doing carefully.

A submarine in the shipping lanes

Chapter 1 introduces one more idea here, and it is worth previewing even though its full treatment waits for Module 7: the Virtual Private Network (VPN).

The book's analogy, retold in our words: picture the Internet as an ocean. Ordinary traffic crosses it like ships on the surface — anyone watching the shipping lanes can see who sails where. Now suppose you need to cross without being observed: you take a submarine. Only the port you left and the port you arrive at ever know about your journey; observers along the way see nothing but water.

A VPN is the submarine. It hides your data's journey by wrapping each packet inside another packet — a technique called tunneling — and encrypting the contents, so that observers along the route can see only the outer wrapper, addressed to a VPN server, and learn nothing about what is inside or where it is ultimately going. Two offices, or a remote worker and a company LAN, can use this to build a private connection over the completely public Internet — a private network that exists virtually, hence the name. That is all you need for now; the machinery arrives in Module 7.

The rest of the family: PAN, WLAN, CAN, MAN

Between the LAN and the WAN, the industry names several other "area networks." The two-question test — reach and ownership — sorts them all.

Two footnotes to the table. First, a WLAN is not a separate network from your LAN — it is the radio portion of it; in most homes the WLAN is effectively the LAN, with only a cable or two left. Second, you will sometimes see VLAN (Virtual LAN) listed alongside these, but it is a different kind of thing entirely: not a size category, but an administrative trick for dividing one physical LAN into several separate broadcast domains by configuration. It belongs to the switching story, and Module 3 tells it properly.

Activity: Label your LAN boundary and WAN link

A diagram activity — pen and paper, nothing to configure.

Objective. Turn your Lesson 1 inventory sketch into a labeled boundary diagram that shows exactly where your LAN ends and your rented WAN link begins.

Setup. Your sketch from the Lesson 1 activity; pen and paper or a drawing app. Optional but helpful: go look at the actual equipment where your Internet line enters your home.

Steps.

1. Redraw your Lesson 1 sketch with room to spare around the edges.
2. Identify the device where your provider's line arrives — a modem, a fiber terminal (often labeled ONT), or a combined provider box. Add it to the drawing if it was missing.
3. Draw one closed dashed curve around everything you own and administer: all your devices, your router, your mesh pods or switch. This curve is your LAN boundary.
4. Draw the single line that leaves the curve toward your provider, and label it WAN link (rented).
5. Write mine inside the curve and provider's outside it.
6. If one combined box is both your modem and your router, draw the boundary through the middle of the box and note that both roles live in one device: the LAN side (Wi-Fi and Ethernet ports) is yours to manage; the WAN side (the port where the provider's line arrives) is the border.

Expected result. One closed boundary containing every device from your inventory, with exactly one line crossing it (two, if you have a backup connection such as a mobile-data fallback).

Verify. Two mental tests. Ownership test: everything inside the curve is equipment you could reconfigure, rename or unplug yourself. Outage test: if your provider has an outage, everything inside the curve can still communicate — you can print, cast to the TV, move files between laptops — while nothing can cross the boundary. If you have experienced an outage like this, you have already felt where the boundary is.

Questions.

1. Which side of your boundary is the provider's box on, and why did you place it there?
2. If you use mesh Wi-Fi pods, are the pod-to-pod connections part of the LAN or the WAN? Why?
3. If you added a backup Internet connection over mobile data, where would the second crossing be on your diagram?
4. When something breaks on each side of the line, who is responsible for fixing it?

If it goes wrong.

• You cannot find where the provider's line enters. In apartments, look for a labeled wall port (fiber or coax); with fixed-wireless or satellite service, the "line" is a radio path — the boundary crosses at the antenna unit.
• An all-in-one provider box blurs the boundary. That is normal: the box contains both a WAN-side role and a LAN-side role. Draw the boundary through it.
• Mobile-only home Internet. There is still a WAN link — the radio path from your 5G router to the provider's tower. Rented reach is what makes it WAN, not the presence of a cable.

Check yourself

1. A hospital owns the fiber connecting four buildings on its own grounds. Which network type is this, and why is it not a WAN despite covering a large area?
2. A law office in Manchester and its branch in Leeds are connected through a telecommunications provider so they can share files. Classify the three networks involved and state what the firm owns versus rents.
3. On your commute, your phone plays audio to your earbuds, then joins your office Wi-Fi, then loads a website hosted on another continent. Name each network type your data touched, in order.
4. A classmate says, "The Internet is basically the world's biggest LAN." Correct the statement using the two-question test.
5. A coffee shop offers free Wi-Fi to customers. What network type are the customers joining, who owns and administers it, and what is the shop's own boundary device toward its provider?
6. During a storm, your video call drops but you can still cast your phone's screen to the TV. Which side of your boundary diagram failed, and how do you know?

Answers

1. A CAN (campus area network). Reach alone does not make a WAN — the hospital owns the links between its buildings; nothing is rented from a provider.
2. Each office runs its own LAN; the connection between them is a WAN link. The firm owns the equipment at both ends (routers, switches, devices) and rents the long-distance middle from the provider.
3. A PAN (Bluetooth to the earbuds), then a WLAN — the wireless part of the office LAN — then the rented WAN link and the mesh of provider WAN links that is the Internet, ending at a distant LAN where the website lives.
4. It fails both questions: nobody owns the Internet (it is thousands of independently owned networks), and it is not one location. The Internet is a mesh of WAN links between providers — an inter-network, not a large LAN.
5. Customers join the shop's WLAN, which is part of the shop's LAN; the shop owns and administers it (chooses the network name, the password, the router). The boundary device toward the provider is the shop's modem/ONT or combined provider box, where the rented WAN link begins.
6. The WAN side. Devices inside your LAN can still reach each other (the cast works), so the LAN is healthy; what failed is the rented link or something beyond it — the provider's side of the boundary.

Key terms

• LAN (Local Area Network) — a network in a single location, fully owned by the organization that uses it.
• WAN (Wide Area Network) — a network connecting distant locations over links rented from a service provider.
• WAN link — the rented connection itself; your home's Internet line is one.
• Router — the device that connects separate networks, forwarding data between them while blocking broadcasts (preview; Modules 3 and 5).
• Internet — the global mesh of WAN links joining the world's providers; a network of networks.
• ISP (Internet Service Provider) — the company you rent your WAN link from.
• VPN (Virtual Private Network) — a private connection built across the public Internet by tunneling and encryption (preview; Module 7).
• Tunneling — carrying a packet hidden inside another packet.
• PAN (Personal Area Network) — a network of one person's devices within a few meters, e.g. Bluetooth.
• WLAN (Wireless LAN) — the radio portion of a LAN; in most homes, effectively the whole LAN.
• CAN (Campus Area Network) — a network of several buildings on one property, with organization-owned links.
• MAN (Metropolitan Area Network) — a city-scale network, typically run by a government or utility.

Summary

• The LAN/WAN distinction is about ownership as much as distance: you own the LAN, you rent the WAN.
• A LAN is one location, all yours; a WAN joins distant sites over provider links you pay for — including your home's Internet line.
• Networks must stay limited in size because shared media have physical limits; routers connect networks while blocking broadcasts, keeping each one manageable.
• The Internet is a mesh of WAN links between providers — no center, no owner, an inter-network.
• A VPN crosses that public mesh privately, like a submarine under the shipping lanes, by tunneling and encrypting packets.
• PAN, WLAN, CAN and MAN complete the size ladder, and the two-question test (reach + ownership) classifies them all.
• Your entire home network sits inside one LAN boundary that exactly one rented link crosses.

Next lesson

You can now classify networks by reach and ownership. Next we look at their shape: the classic topologies — bus, ring, star and mesh — and why almost every network you will ever touch is built as a star.

Sources and further study

• Network Essentials, Dr. Tahseen Al-Doori — Chapter 1, "Introduction to Networking": LAN vs WAN, the rented-link framing, the Internet figure, the VPN analogy and the area-network definitions.
• Cisco Networking Academy — Networking Basics (free course): the same LAN/WAN taxonomy as taught by the industry's largest academy program.
• Cloudflare Learning Center — "How does the Internet work?": a clear, current explanation of the provider mesh your WAN link attaches to.