Mesh Wi-Fi

Wi-Fi dead zones and the limits of a single AP

A small home network often uses one wireless router with an integrated access point. This arrangement is simple, but coverage depends on the device location, transmit power, receiver sensitivity, channel width, and obstacles. Signals in the 5 GHz and 6 GHz bands usually attenuate more through walls and floors than 2.4 GHz signals, although the material, geometry, and interference determine the result. A router can have a high WAN rate while a distant client still receives a lower radio rate.

The result can be a Wi-Fi dead zone, an area where the signal is too weak for stable operation or is not received. It may occur in a corner bedroom, a basement office, or a patio. A lower radio throughput does not automatically indicate a problem with the provider link because it limits the segment between the client and AP. A single router can therefore leave poor coverage in a large or multi-story building even when the Internet service has a high rate. Channel width, active stations, and interference-driven retransmissions also affect the result. A speed test made beside the router measures a different radio path from one made behind two concrete walls. The radio result describes local access, while the provider connection is a separate path.

Range extenders and radio retransmission

One way to extend coverage is a Wi-Fi range extender, also called a repeater. It is placed between the router and the weak-signal area. The extender receives frames from the Wi-Fi network and retransmits them. This can reach a previously uncovered place, but it adds another radio segment and depends on the link between the extender and the router.

In a common single-radio extender operating on one channel, reception and retransmission cannot use the same airtime. Some of the airtime is spent on the second hop, so the throughput available to a client falls. A simplified model often uses $50\%$, but that value is not fixed for every device. Two radios, another channel, or a wired backhaul changes the result. An extender can use a separate SSID such as "HomeNetwork_EXT", but a shared name is also possible. A shared SSID does not guarantee roaming because the client usually decides when to change its AP. Extender placement affects both the signal received from the router and the signal sent to the client. Its uplink can therefore become the limiting link even when the client has a strong signal from the extender.

Wi-Fi mesh topology and its nodes

A Wi-Fi mesh system uses several connected devices, called nodes or satellites. The nodes provide access in different places, while a controller or vendor software can coordinate their configuration. Coverage and throughput depend on node placement, the backhaul, and radio conditions.

A typical mesh system can include these elements:

• The primary node and gateway: One node can operate as a router and connect to a modem, optical network terminal, or another provider device. In router mode it forwards packets between the local and external networks. In AP mode another device can perform routing.
• Satellite nodes: The remaining nodes provide APs in other parts of the building. They can connect to the primary node through Ethernet or a Wi-Fi backhaul. Some systems support forwarding between satellites, while others use a direct link to the primary node.

A system can create a mesh topology. This does not mean that every node maintains a link to every other node. A client can associate with a selected AP, and a controller can use a link to the primary node or another hop. A path is not necessarily the fastest measured route because metrics, load, configuration, and multihop support determine the choice. Star, tree, and multihop arrangements are all possible, and the word mesh alone does not identify the path algorithm. The controller may prefer a stable link with lower capacity over a congested link with a higher nominal rate.

Mesh backhaul, path selection, and client transitions

Mesh behavior depends on the links between nodes, path selection, client handling, and configuration management.

• Wireless backhaul

  The link between mesh nodes is called the backhaul. With a radio backhaul, node traffic competes for airtime with client traffic unless the hardware has a separate radio. Many tri-band systems have one 2.4 GHz radio and one 5 GHz radio for clients, plus another 5 GHz or 6 GHz radio used mainly for the backhaul. Availability of a 6 GHz radio backhaul depends on regional rules, device certification, and configuration. This is a hardware option, not a mesh requirement. A dedicated radio still leaves limits from signal level, channel width, interference, hop count, and load. In a simplified single-radio model, client airtime can fall to about $50\%$ of the value without retransmission, but the actual result depends on traffic and hardware. Adding a satellite therefore does not guarantee the same throughput.

• Path selection and reconfiguration

  A controller or node can collect information about signal level, link availability, and load. The implementation can then select a path or change it after a failure. IEEE 802.11s defines one method for building a multihop mesh network, while a commercial system can use vendor control or an EasyMesh profile. There is no single rule that always chooses the fastest route and maintains service after every failure. Reconfiguration depends on the metrics, timers, and recovery procedures implemented by the system.

• Roaming and band steering

  A shared SSID lets a client consider another AP, but it does not force a transition. Roaming can use 802.11k for measurements and neighbor information, 802.11v for BSS management suggestions, and 802.11r for a faster BSS transition when both the client and infrastructure support them. These mechanisms do not guarantee a handoff without a pause because the client participates in the decision. Band steering is a vendor or controller policy. It can suggest 5 GHz instead of 2.4 GHz when the signal is suitable, but the result depends on the location and client.

• Management and expansion

  Consumer systems often provide one configuration interface that lists nodes and clients and exposes network settings. The available functions depend on the vendor. Adding a satellite requires a compatible model, software version, power, and suitable placement. Automatic integration depends on the system and supported topology. After the node arrangement changes, the controller may need time to measure links and establish new paths.

Ethernet backhaul

An Ethernet backhaul carries traffic between nodes over a cable. Many mesh systems support this option. If a building has Ethernet cabling, satellite nodes can connect to the primary node or to a switch according to the system requirements.

An Ethernet backhaul removes the radio hop between nodes and leaves more airtime for clients. Its result still depends on the wired infrastructure:

• Throughput between nodes follows the negotiated port rate, cable quality, switches, and load. A gigabit path is not guaranteed by the mesh name.
• The wireless channel no longer carries node-to-node traffic, so more airtime remains for clients. The client-to-AP radio link and the wired path still impose their own limits.

Ethernet backhaul usually makes throughput easier to analyse and reduces dependence on interference between nodes. It does not remove limits from the client, AP, router, or provider link. A cable path can still be limited by a 100 Mbps port, a poorly negotiated link, a switch queue, or the provider connection. Radio conditions still determine the final client rate. Wired and wireless segments require separate measurements.

Wi-Fi mesh and alternative layouts

This comparison separates the effects of node count, backhaul, and management method.

Wi-Fi EasyMesh and interoperability

Many mesh systems use vendor-specific protocols, so adding a satellite can require a compatible family of devices. The Wi-Fi Alliance developed Wi-Fi EasyMesh as a specification for managing multiple access points. It defines logical Controller and Agent roles and permits wired or wireless backhaul.

EasyMesh certification can make cooperation between products from different vendors easier, but the result depends on the profile version, supported functions, Controller role, and vendor extensions. EasyMesh is distinct from IEEE 802.11s. 802.11s describes a multihop mesh at the IEEE 802.11 layer, while EasyMesh coordinates multiple APs as a Multi-AP system. The Controller and Agents exchange management information, while user traffic can use Ethernet or Wi-Fi backhaul. A certified profile does not make every feature or every firmware combination interchangeable. The exact implementation should be checked before the devices are combined.