p4f wrote

Now that the EAP615-Wall comes with Mesh support, I'm wondering whether the below setup, mixing wired and wireless backhaul, can work.

 

The choice for the EAP615-Wall is partly due to the need of a wall device as well as cutting corners by employing the extra LAN ports provided by the EAP615 to connect some devices directly to the wireless APs.

 

Many thanks!

Hi @p4f 

If the WiFi coverage of the EAP-Wall series can cover the whole network topology you mentioned, yes they should work via the mesh system.

But please note that the actual wireless data throughput and wireless coverage are not guaranteed. They will vary due to factors including network conditions, client limitations, and environmental factors, including building materials, obstacles, volume and density of traffic, and client location.

  @p4f 

Yes. This is precisely the scenario that makes a wall unit with Mesh capability so interesting, kudos to the TPlink team that dared make it happen :)

  @d0ugmac1 late but additional confirmation... I have 3x EAP650. One as wired root AP (poe from switch). Two as wireless backhaul powered by the PoE injectors supplied with them in the box (no cable to switch) and configured to mesh to the root. Plug them in and they all appear for adoption. Unplug poe from either mesh AP and they show as disconnected. Replug and they get readopted and back online.

  @p4f 

Are you saying, with a wired root and two child wirelessly meshed APs, that if you remove power from either child, then they ALL show as disconnected?

  @d0ugmac1 

No, removing poe from one child results in its status being Disconnected (the root AP stays connected).

Also when you reconnect poe to the child I earlier said it re-Adopts, but I should have said its status shows as Provisioning while it reboots and reconnects to the root AP again (as per Mesh Uplink/Downlink and "favourite" settings).

You have to be patient. The whole reboot / reconnect process can take from 3 to 5 minutes.