Ethernet backhaul is useful when walls or distance weaken wireless mesh, but the cabling must follow the system's supported topology.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
Was global Ethernet-only mode enabled before every node was wired?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Node cannot pair | Check exact model ecosystem, node role and firmware first. |
| Wired backhaul fails | Trace cable order and mode; avoid an upstream loop. |
| Wireless node drops | Move it to a location with a usable uplink, then retest a client. |
Decision after the first test
Compare actual node performance with and without a known-good wired path. Do not add a second upstream path that loops the network.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- UniFi wireless meshing and uplink settings (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.