Last updated:
Ethernet backhaul connects compatible mesh nodes through network cables instead of using a wireless link between those nodes. It can free wireless airtime and help across thick walls or floors. It does not eliminate interference between a phone and its access point, or make every mesh model compatible with every other one.
Check compatibility before choosing equipment
- Confirm wired-backhaul support for the exact router/node models and firmware.
- Check the required port on each node and the speed of every link.
- Check whether mixed wired and wireless nodes are supported in the intended mode.
- Check whether a managed switch, VLAN feature or loop-prevention behavior affects the vendor’s mesh traffic.
TP-Link provides Deco Ethernet-backhaul wiring instructions. ASUS documents AiMesh Ethernet Backhaul Mode and connection priority. These are supported families to investigate, not proof that every device carrying the brand can join the same mesh.
Router-mode topology
In a typical supported router-mode arrangement, the internet connection goes to the main mesh router. Its LAN connects to a switch, and compatible satellites connect on that LAN side. Do not place satellites beside the main unit on an upstream ISP-side switch if the manufacturer requires them behind the main router.
For example: ISP connection → main mesh router → LAN switch → wired satellites. This is an illustrative path; the vendor’s port and topology instructions take precedence. Avoid adding a second cable that creates an unintended loop.
Access-point mode with an existing router
If keeping the provider’s router for routing and DHCP, a supported mesh AP mode can avoid a second routed network. The existing router’s LAN supplies the mesh units according to the vendor’s supported topology. Some router-only functions disappear in AP mode.
TP-Link’s Deco AP-mode instructions explain the mode change and feature differences. Our DHCP guide helps identify which device should allocate addresses. Do not leave an unintended second DHCP server on the same LAN.
Port speed is part of the backhaul
A Gigabit Ethernet port gives a different ceiling from a 2.5GbE or 10GbE port. The slowest relevant port, cable link or switch path can limit a transfer. A mesh node’s advertised aggregate wireless rate is not the same as the throughput available through one Ethernet port.
Our 10GbE switch guide explains mixed-speed ports. A faster switch alone cannot upgrade a node that only has a slower Ethernet interface.
When a node still shows wireless backhaul
- Confirm that the node has joined the supported mesh and has current firmware.
- Inspect the cable, negotiated link and required satellite port.
- Check that the switch is on the correct side of the main router.
- Test a direct connection temporarily to separate a switch issue from a node/cable issue.
- Use supported per-node priority or Ethernet-only settings only when the required nodes are actually wired.
Check the app’s actual topology status after changes, and repeat the latency comparison under the same conditions. If printers or local devices stop communicating, inspect guest and AP-isolation settings rather than assuming the backhaul cable is faulty.