Compare UniFi mesh and wired access points

Goal and prerequisites

Measure how the access point's backhaul affects your own installation. Backhaul is its connection to the rest of the network. This exercise measures wireless first, then changes the same remote AP to Ethernet while preserving its position and test workload.

Use an existing, adopted wired AP named AP-Parent, and a new or spare supported AP named AP-Remote that is already at factory defaults. The remote must not be serving production clients. Keep the parent's working configuration and existing management network. Both APs will be managed by the same UniFi Network application; standalone AP mode does not support this meshing exercise. [2] [4]

Prepare a compatible PoE injector for the remote, a temporary Ethernet cable and the wired local iperf3 server from Slow WiFi diagnosis guide. Initially leave the injector's LAN input disconnected: its powered output connects to the remote AP, supplying power without an Ethernet data path. Check that the chosen AP supports wireless uplink before proceeding.

Adopt the remote AP wirelessly

  1. Prepare the parent. Confirm AP-Parent is online with a wired uplink. Under Settings › WiFi, enable Wireless Meshing. In UniFi Devices › AP-Parent › Settings, enable Mesh Parent and leave Mesh Connect disabled on this wired AP. The dedicated mesh guide assigns Mesh Parent to the source and Mesh Connect to the wireless child. [1]
  2. Power the factory-default remote nearby. Place AP-Remote close to the parent for initial adoption, with its injector LAN input still empty. Open the site's UniFi Devices list or mobile app, wait for discovery and select Adopt for the new AP. Ubiquiti's wireless-adoption workflow calls for a powered new AP near the wired uplink AP with site meshing enabled. [4]
  3. Confirm the wireless role. Wait until adoption and any required update finish. Name the remote and inspect its settings: Mesh Connect must be enabled for its wireless uplink. Confirm the displayed parent is AP-Parent and the path has one wireless hop. Record both models, firmware versions and the test SSID. [1]
  4. Choose the measurement position. Move the remote to the proposed installation point while retaining power without Ethernet data. Check its parent signal; Ubiquiti recommends approximately -60 dBm or stronger. If relocation is necessary, establish the new final position before recording either result set. Mark the client position nearby and confirm it associates with AP-Remote. [1]

Measure wireless backhaul

  1. Keep the local test path consistent. Use the same client, SSID, VLAN and wired server throughout. Start the server with iperf3 -s. Allow its local test traffic as described in Slow WiFi diagnosis guide. Replace SERVER_IP below with that server's actual address, then run each command three times, one run at a time. The second command reverses traffic direction. [3] 
iperf3 -c SERVER_IP -t 30
iperf3 -c SERVER_IP -t 30 -R
  1. Record useful observations. For each direction, save all three results and their median. Record client band, signal, parent link and any interruptions during a representative activity such as a video call. Check client association immediately before each run. If it changes to the parent, repeat that run after restoring the intended association. Keep unrelated heavy traffic as similar as practical between the two stages.

Change to wired backhaul

  1. Disable the wireless child role first. While AP-Remote is still reachable over mesh, open its settings, turn off Mesh Connect and save. It may become unreachable after applying that change. This is expected during this controlled transition. Do not enable Mesh Connect on an AP that is already using a wired uplink. [1]
  2. Add the Ethernet data path. Connect the prepared switch cable to the injector's LAN input. Keep the injector, AP and client at the recorded positions. Use the correct management native network and test-VLAN permissions on this switch port. Wait for the remote to return online, then verify a wired uplink and confirm Mesh Connect remains disabled.
  3. Repeat the identical measurements. Confirm the client is back on AP-Remote, with the same SSID and band. Repeat both commands three times and the same application test. Record negotiated Ethernet speed. If a radio channel, client band or background workload changed, note that limitation or repeat under comparable conditions.

Compare and verify

Check Wireless backhaul Wired backhaul
Uplink evidence Parent and signal Switch port and link speed
Client to server Median of three runs Median of three runs
Server to client Median of three runs Median of three runs
Application Interruptions and usability Interruptions and usability

Choose against the workload's actual requirements. Do not treat one quiet-period result as a capacity guarantee. Repeat the important activity during a representative busy period and retain the results with the topology.

If initial wireless adoption fails, check model support, parent role, site meshing, proximity and power before retrying; leave production APs intact. If the wired transition fails, inspect the prepared cable, switch port and VLAN path. Leave the test AP in the verified wired state after the comparison, pending the chosen permanent installation.

Sources

Back to the series

Leave a comment

Please note, comments need to be approved before they are published.