Mesh networking

What is a mesh network?

A mesh network is a network in which devices connect directly to the devices near them and pass traffic along for each other, instead of all connecting to one central point. At home, "mesh Wi-Fi" means several access points that relay for each other so one network covers the whole house. A message can travel through several devices to reach one that is out of direct range, and when a device drops out, traffic can take another path.

TL;DR

A mesh has no single centre to fail, so it keeps working when part of it breaks, covers ground no single radio could, and lets nearby devices talk directly. In exchange, relays spend battery and airtime, each hop adds delay and loss, and messages need end-to-end encryption. A mesh reaches the internet only through a gateway device.

Learning objectives

After reading this article you will be able to:

  • Distinguish a mesh network from a star network built around one centre
  • Describe how a message moves through a mesh by flooding or routing
  • Recognise the costs of a mesh in battery, airtime, delay and security

Mesh Wi-Fi vs mesh network

Mesh Wi-Fi is one kind of mesh network: the access points relay for each other, and your phones and laptops stay ordinary clients. In a device mesh, the devices themselves relay, so the network can exist with no access points at all.

A home mesh Wi-Fi system such as Google Wifi puts a primary unit on the modem and adds more units around the building. The Wi-Fi Alliance describes these systems as several access points that work together as one network and steer each device to the best one. Your phone connects to whichever unit is nearest, but it never carries traffic for anyone else. Wireless mesh network vs mesh Wi-Fi at home compares the two in detail, and the rest of this article is about the wider idea: a network in which the devices themselves relay.

Mesh network vs star network

A star network sends every message through one centre, while a mesh has no single centre. Most networks people use every day are stars. Phones connect to a cell tower, laptops connect to a Wi-Fi access point, and every message passes through that centre on its way somewhere else. The centre is convenient: it knows where everyone is, and it can be managed in one place. It is also the part that fails. When the tower loses power or the access point goes down, every device that depended on it loses the network at the same moment.

In a mesh there is no single centre. Each device, often called a node, keeps links to the nodes within its radio range. Those links overlap, so the network is a web of short connections rather than a set of spokes. A node that receives a message meant for someone else can forward it, and the message moves hop by hop toward its destination.

In a star, every device depends on the centre. In a mesh, each device links to its neighbours, so there is usually more than one way through.

Message flow through a mesh network

Three things have to happen for a message to cross a mesh: nodes find their neighbours, the network picks who carries the message next, and something stops the message living forever. First, nodes discover their neighbours, usually by broadcasting short announcements and listening for others. Second, the network decides which neighbour carries each message next. Some meshes flood: every node rebroadcasts what it hears, which is simple and copes well with change but uses a lot of airtime. Others route: nodes learn paths and send each message along a chosen one. Third, the network stops messages from living forever. Messages carry a hop limit, often called a time to live (TTL), and a unique identifier, so nodes can drop copies they have already handled.

How does a message cross a mesh network? goes through each step in detail.

Types of mesh network

The main kinds are mesh Wi-Fi systems, Thread, Zigbee, Bluetooth Mesh, LoRa meshes such as Meshtastic, mobile ad hoc networks, and application-level meshes on phones and computers. Mesh is a shape, not a single technology, and they differ most in who does the relaying and whether a phone can take part:

Kind of meshWho relaysRadioTypical useNeeds a hub or router?Can a phone be a node?
Mesh Wi-Fi systemThe access pointsWi-FiOne Wi-Fi network across a whole home or officeYes, a primary unit on the modemNo, phones stay clients of the access points
ThreadAlways-on routers; end devices do not forwardIEEE 802.15.4 at 2.4 GHzLow-power home and building devices, including Matter devices that run over ThreadA border router to reach Wi-Fi, phones and the internetNo, phones have no 802.15.4 radio and reach Thread devices over IP
ZigbeeThe coordinator and routers; end devices do not relayIEEE 802.15.4, at 2.4 GHz and in sub-GHz bandsSmart home devices, smart meters, commercial buildingsA coordinator forms each networkNo, phones reach it through a hub or over Bluetooth LE with Zigbee Direct
Bluetooth MeshNodes with the Relay feature, by managed floodingBluetooth LENetworked lighting control and building automationNo central controllerNot usually; a phone without a mesh stack joins through a proxy node over GATT
LoRa mesh, such as MeshtasticEvery radio rebroadcasts what it receivesLoRaLong-range, off-grid text messagingNoNo, a phone pairs with a radio over Bluetooth, Wi-Fi or USB
Application-level phone meshThe phones and computers running the appThe links the devices already have, such as Bluetooth LE and local Wi-FiApps on nearby phones coordinating directlyNoYes, the phone is the node

In more detail:

  • Wi-Fi mesh. IEEE 802.11s defines mesh networking between Wi-Fi stations, and home mesh Wi-Fi systems use a set of access points that relay for each other. The phones and laptops you connect are still clients of those access points.
  • Bluetooth Mesh. The Bluetooth SIG publishes a mesh specification built on Bluetooth Low Energy for lighting, sensors, and building control. It relays messages by managed flooding, and later versions add directed forwarding.
  • Thread and Zigbee. Both run on IEEE 802.15.4 radios and form low-power meshes for home and building devices. Thread carries IPv6, and Matter, the smart-home application standard, can run over it. What is Thread? covers its roles and border routers, and How does Zigbee work? covers coordinators and routers.
  • LoRa meshes. Meshtastic uses inexpensive LoRa radios that rebroadcast the messages they receive, trading bandwidth for range. What is Meshtastic? explains how it works.
  • Mobile ad hoc networks. The IETF has published routing protocols such as AODV (RFC 3561) and OLSR (RFC 3626) for networks of moving devices with no fixed infrastructure.
  • Application-level meshes. Software on phones or computers can build a mesh over links the devices already have, such as Bluetooth Low Energy or a local IP network, and handle discovery and routing itself.

Mesh network advantages

A mesh keeps working when part of it fails, because there is usually more than one path. It can cover ground no single radio could, because each hop is a short link. It grows with the number of devices present instead of depending on one piece of fixed infrastructure. And it lets nearby devices talk to each other directly, without a round trip to a distant server.

That makes mesh a natural fit where infrastructure is missing, overloaded, or untrusted: disaster zones, crowded venues, ships, mines, farms, and industrial sites.

Mesh network trade-offs

A mesh is not free: every relay spends battery and airtime on other devices’ traffic. Each hop adds delay and another chance of loss, so long routes are slower and less reliable than short ones. Coverage depends on where devices happen to be, which changes as they move. And because messages pass through devices the sender does not control, a mesh needs end-to-end encryption and a way for devices to prove who they are, so relays carry content they cannot read.

A mesh also does not create internet access on its own. If one device has a connection and is set up as a gateway, the mesh can reach the cloud through it. Otherwise the mesh is a local network, which is often exactly what is needed.

Frequently asked questions

Does a mesh network need the internet?

No. A mesh is a local network between the devices in it. It can reach the internet only if one of its devices is set up as a gateway with its own connection; otherwise devices in the mesh can still reach each other, but not the cloud.

Is Thread a mesh network?

Yes. Thread is an IPv6 mesh for low-power devices on IEEE 802.15.4 radios in the 2.4 GHz band. Always-on routers forward traffic for the other devices, and a border router connects the mesh to other networks such as Wi-Fi.

Is a mesh network secure?

It can be, but the shape alone does not make it so. Messages pass through devices the sender does not control, so a secure mesh encrypts content end to end and lets devices prove who they are with keys, so relays carry ciphertext they cannot read.

Which standards use mesh networking?

IEEE 802.11s defines Wi-Fi mesh, the Bluetooth SIG publishes Bluetooth Mesh, Thread and Zigbee run on IEEE 802.15.4 radios, and the IETF has published routing protocols such as AODV and OLSR for mobile ad hoc networks. Software on phones or computers can also build a mesh at the application level.

Are longer routes through a mesh slower?

Yes. Each hop adds delay and another chance of loss, so long routes are slower and less reliable than short ones.

Where are mesh networks used?

Mesh is a natural fit where infrastructure is missing, overloaded, or untrusted, such as disaster zones, crowded venues, ships, mines, farms, and industrial sites.

Sources

Build it with Offline Protocol

The Offline Protocol mesh SDK forms an application-level mesh between devices over Bluetooth LE, local IP networks, and an internet relay, with routing, acknowledgments, and MLS encryption built in. The transport docs list what each path supports in the current release.

Read the transport and routing docs