Network Types & Topologies — The Blueprint Behind Every Connection

If you’ve ever wondered what actually holds a network together beneath the surface, this is where it starts. Before we talk about protocols, security tools, or cloud infrastructure, we need to understand the physical and logical blueprints that define how networks are built.

What Is a Network, Really?

At its core, a network is just a collection of devices that can communicate with each other. But the way those devices are organized — and the geographic scope they cover — determines what kind of network you’re dealing with.

LAN (Local Area Network) — A LAN connects devices within a limited physical area, typically a single building or floor. Your home Wi-Fi is a LAN. Your office network is a LAN. LANs are fast, relatively inexpensive to build, and easy to manage.

WAN (Wide Area Network) — A WAN connects multiple LANs across large geographic distances — cities, countries, or even continents. The internet itself is the largest WAN in existence. WANs typically rely on third-party ISP infrastructure and carry higher latency than local connections.

MAN (Metropolitan Area Network) — A MAN sits between a LAN and a WAN in terms of scale. It connects networks across a city or campus. Universities, large municipalities, and multi-building corporate campuses often use MANs to link facilities without going through a public ISP.

Network Topologies

Topology describes how devices are physically or logically arranged and how data flows between them. Each topology has its own tradeoffs in cost, performance, and fault tolerance.

Bus Topology — All devices share a single communication line. Simple and inexpensive, but a failure anywhere on the bus can disrupt the entire network. Rarely used in modern deployments.

Ring Topology — Devices are connected in a closed loop. Data travels in one direction around the ring. A single failure can break the entire circuit unless the network uses a dual-ring design for redundancy.

Star Topology — All devices connect to a central switch or hub. This is the dominant topology in modern networks. If one device fails, the rest keep running. The tradeoff is that the central switch becomes a single point of failure — which is why enterprise environments use redundant switching.

Mesh Topology — Every device connects to every other device. Full mesh provides maximum redundancy but is expensive and complex to manage. Partial mesh is a common compromise, connecting critical nodes fully while leaving others with fewer redundant paths.

Why This Matters

Understanding network topology isn’t just academic. When you’re troubleshooting a connectivity issue, designing a new office network, or assessing the blast radius of a potential failure, topology is the map you’re working from. Knowing that your environment runs a star topology with a single core switch tells you immediately where the highest-risk point of failure lives.

For security professionals specifically, topology shapes your segmentation strategy. Where you place firewalls, how you define network zones, and where you deploy monitoring sensors all depend on understanding the physical and logical layout of your environment.

Start here. Everything else builds on it.

References

  • IEEE 802 LAN/MAN Standards Committee. IEEE 802-2014: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture. IEEE, 2014. https://standards.ieee.org/ieee/802/3948/
  • Tanenbaum, Andrew S., and David J. Wetherall. Computer Networks, 5th ed. Prentice Hall, 2010.
  • Forouzan, Behrouz A. Data Communications and Networking, 5th ed. McGraw-Hill, 2012.
  • Cisco Systems. “Network Topologies.” Cisco Networking Academy. https://www.netacad.com
  • IETF RFC 1122 — Requirements for Internet Hosts — Communication Layers. https://www.rfc-editor.org/rfc/rfc1122