@wahawkIA 

 

hi. had LOTS of issues configuring eth backhaul with 3 M5.

tried many thigs over the course of several weeks and in my frustration ended up solving it by -

1. "wiping" (factory reset" all 3 of them individually

2. updating their firmware individually (prior to setup)

3. setup and - bingo

 

it has been working flawlessly ever since version 1.4.2

 

quick note - I have them setup as AP and I use Netgear switches

@AnonyOne 

 

Thanks for the reply.  I originally set these up to have signal source be Wifi.  Thought I could get better performance using Ethernet backhaul.  Tp-Link support has escalated the issue.  We'll see what they come up with.  Thanks again for the reply.

@TP-Link_Deco 

 

I may have this fixed.  My Dell switch had Spanning Tree turned on globally.  I disabled this function and now looks like both slave Decos are connected to Ethernet backhaul.  Letting it run to see if there are no issues.

@TP-Link_Deco 

 

Whilest all slave Decos are now connecting via Ethernet, one randomly disconnects/reconnects at times.  may try a different patch cable at the switch, or a different port on the switch.

yes I did the same. disabled on only on the port that the slave Deco M5 is connected. Switch was disabling it as an "alternate" RSTP port as I think it thinks a loop has occurred. Probably received BPDUs from there.

@TP-Link_Deco 

> Some managed switches have an option to prevent loopback traffic in the network. When Decos are connected to the switch, they will maintain the Wi-Fi backhaul until the Ethernet Backhaul is established. Once they're connected, there is a very short time period in which both Wi-Fi connection and Ethernet connection are established between Decos and the switch may regard it as loopback traffic and block the Ethernet connections between Decos.

 

I'm guessing this is why my Dell PowerConnect sees a spanning tree STP loop and disables the ethernet port connected to the slave deco as an "alternate" RSTP port. hence deco cannot establish ethernet backhaul.

 

had the same problem where slave deco cannot establish ethernet backhaul.

I disabled STP on the port where the slave deco is connected. now it can have an ethernet backhaul.

however, obviously Deco shouldn't really foward any packets received on the wireless interface to the ethernet interface. Basically bridging the two. It should have been either or. but obviously I guess it is also trying to use IEEE 1905.1 where it probably can use the both but I don't know much about that to be honest.