WAN, LAN, PAN, and MAN

PAN, LAN, MAN, and WAN are network categories defined mainly by scope, ownership, and the kind of links they depend on. The size difference matters, but the operational model matters even more.

A PAN, or personal area network, is the smallest. It usually covers a few metres around one person or device cluster. Bluetooth earphones connected to a phone, a smartwatch paired with a laptop, or a wireless keyboard linked to a tablet are common examples. PANs are short-range, low-power networks designed for convenience. Their constraints are battery life, radio interference, and limited bandwidth rather than complex routing.

A LAN, or local area network, covers a home, office, floor, building, or sometimes a single campus under one organisation’s control. Ethernet and Wi-Fi are the usual technologies. A LAN is where devices share printers, file servers, switches, and internet access. Because the environment is local and centrally managed, LANs usually offer lower latency and higher bandwidth than wider network types. The failure domain is also more contained. A bad switch or misconfigured VLAN may disrupt one office in Berlin without affecting another site.

A MAN, or metropolitan area network, sits between LAN and WAN. It connects sites across a city or a large urban campus. A university with buildings across Manchester, a city council linking offices and transport depots, or a metro fibre ring run by a provider are typical examples. MANs often use provider-managed fibre, dark fibre, or dedicated metro Ethernet links. They are still relatively fast, but they depend more on carrier infrastructure and right-of-way than a simple in-building LAN.

A WAN, or wide area network, spans large regions such as countries or continents. The public internet is the best known WAN, but private corporate WANs also exist using MPLS, leased lines, SD-WAN overlays, or encrypted tunnels over broadband links. A WAN is built for inter-site connectivity across distance, not for the low-latency assumptions common inside a local network.

The network type affects engineering choices.

• Latency and jitter usually rise as the network gets wider and depends on more intermediaries.
• Ownership becomes less direct. A PAN or LAN is often fully under your control. A MAN or WAN often crosses provider boundaries.
• Failure modes broaden. A LAN outage may be a local switch fault. A WAN outage may involve carrier routing, fibre cuts, or internet path instability.
• Security posture changes. Traffic on a PAN or LAN may still need encryption, but WAN links are where organisations most often rely on VPNs, private circuits, or zero-trust access controls.

These terms are useful as rough classes, not rigid laws. A large campus LAN can look MAN-like. A VPN can make remote users behave as if they are on one logical enterprise network even though the physical transport is WAN. Still, the categories help predict what will dominate design and operations: radio constraints in a PAN, switching and local segmentation in a LAN, carrier-managed metro transport in a MAN, and distance plus provider dependency in a WAN.