Wi-Fi access point vs mesh

What is the real difference?

An access point connects wireless clients to the wired network. In a wired design, every access point normally reaches the switch through Ethernet. In a wireless mesh, at least some access points reach the network through another radio node instead. Cisco Meraki calls these nodes repeaters and describes the gateway as an access point with a direct wired connection.

Both designs may present one network name and support roaming. The dividing line is backhaul, not the shape of the plastic enclosure. Product marketing often blurs that point, so draw the data path for every node.

Sources: Cisco Meraki Documentation, Cisco Meraki Documentation

When is mesh a sensible compromise?

Mesh helps in a finished building where cable routes are blocked, civil work is unacceptable and the wireless path between nodes is strong. It can also bridge a difficult area temporarily while a proper route is planned. The mesh node still needs power, ventilation and a useful radio position.

Avoid daisy chains when possible. Every extra wireless hop adds contention and another failure point. The precise performance depends on radios, channels, client load and construction, so a universal speed promise would be fiction. Test at the intended positions with the doors shut and the building occupied normally.

Sources: Cisco Meraki Documentation, Cisco Meraki Documentation

How should access points be placed?

Place for users and obstacles, not for symmetry on a reflected ceiling plan. Dense masonry, metal, mirrors, lift cores and service shafts change the radio path. A corridor-mounted access point may look tidy while rooms behind two walls remain weak.

Capacity matters as much as signal. A boardroom full of laptops and phones is a different problem from a quiet bedroom. Record expected devices, applications and guest access, then verify coverage and roaming after installation. Bars on a phone are not a handover test.

What should be documented at handover?

Keep the floor plan with access point names, cable labels, switch ports and mounting positions. Record the management account, firmware policy, network names, VLAN purpose and guest isolation. If a mesh hop remains, mark its parent path so a future technician can see what changed when a node moves.

Run a short acceptance test in each agreed area. Check association, internet reachability, local services and a roaming walk where movement matters. The result is a baseline. Without it, every future complaint starts as an argument about memory.

Sources: Cisco Meraki Documentation

How should you draw the backhaul path for every radio?

Give every access point a name and trace its path back to the network. A wired access point reaches a switch through its Ethernet connection. In the Cisco Meraki mesh terminology used by the existing guide sources, a gateway access point has the wired connection and a repeater reaches the network over a wireless mesh path. The same network name on several radios does not tell you which of those paths a device is using.

On the floor plan, mark the wired switch port for each gateway or wired access point. For a repeater, mark the intended upstream radio and note that moving either node can change that relationship. Avoid treating a decorative placement as final until the proposed path is tested in the actual building. Walls, doors and occupancy can affect the useful radio path. The drawing should expose dependencies for troubleshooting; it should not claim a speed or coverage result before a survey and acceptance test establish one.

Sources: Cisco Meraki Documentation, Cisco Meraki Documentation

What does a useful acceptance record contain?

Agree the test areas and expected uses before installation. A bedroom, work area and room with several active devices do not represent the same demand. At each agreed location, record which access point the client uses, whether required local resources are reachable and whether the internet path works. Where movement matters, walk the intended route and observe whether the client remains usable as it changes its radio association.

Keep the client model and test conditions with the result because roaming decisions and radio capability also belong to the client. If a mesh repeater is used, record its gateway or parent path at the time of the test. Save the access point names, mounting positions, switch ports and relevant configuration ownership beside the results. This creates a baseline for later diagnosis. It is not a universal throughput guarantee, and it should be repeated when a node moves, the layout changes or the agreed use changes materially.

Sources: Cisco Meraki Documentation, Cisco Meraki Documentation

Use the decision table

Choose the column that matches the building and operating responsibility. If the answers land in different columns, write down the compromise before buying equipment.