BE25 does not support backhaul over switch ???

BE25 does not support backhaul over switch ???

BE25 does not support backhaul over switch ???
BE25 does not support backhaul over switch ???
2025-05-14 11:11:09 - last edited 2025-05-15 10:45:54
Model: Deco BE25  
Hardware Version: V7
Firmware Version: Latest

Hi Deco community,

 

I've had Deco Mesh at home for 5+ years and have been super happy with it till now. I love the user interface of the app, the ease in which it can all be setup from scratch, and the way I can remote monitor my home network when away.

 

I just upgraded my ISP connection to a 2.5/2.5Gbps FTTH and was looking for a router that could connect to the ONT at 2.5gbps and to my LAN at 2.5Gbps (so I need minimum of 2x 2.5gbps Ethernet ports). Most devices around the home are Wifi 6/6e . The home is 400mq over 3 floors with ethernet (1 x Cat6e) to each floor. Wi-Fi between floors/rooms is not good, hence the need for more or less one device per room. We are luck that the house is detached and there are no other networks creating congestion.

 

My intention was to have a hub and spoke design with a BE25 on each floor (ONT is in the basement where I have a 2.5gbps TP-Link Switch connected to the BE25 Master). On floors 2 and 3 I would have the BE25 backhauled over ethernet to the switch which connects all 3 LAN ports of the BE25s.

 

Over the weekend I brought my 3x BE25s and 3x M5 and 3x M4 to a single location in the basement where I did a FW update and then factory reset everything and created the new network from scratch.

 

My issue is that no matter what I try (different ports/cables etc.) there is no way I can get past the first step, which is to have the BE25s communicate over ethernet backhaul through the TP-Link TL-SG105 switch.

 

BE25 (Master) has port 0 (left) to the ONT at negotiated 2.5gbps and port 1 (right) connected to the Switch

BE25 Slave 1) - first added to the network wirelessly - then has port 0 connected to the same switch as master

BE25 Slave 2) - first added to the network wirelessly - then has port 0 connected to the same switch as master

 

 

In this extremely simple example - there is NO WAY, that I can get the two slaves to show Ethernet backhaul. Due to the concrete floors and distance, it’s a must that the 2 slave devices communicate with the master over 2.5gbps ethernet.


According to this : General questions about Ethernet Backhaul feature on your Deco | TP-Link Italia  - It should be possible.

 

As an experiment (to see if it was a problem with the switch filtering), I added the M5s to the network (first wirelessly) and then connected them to the same switch and hey presto , all three happily connect over ethernet backhaul. Did the same for the M4s and no problem. It's these BE25s that seem not to be able to work in this way. Interesting point that the LEDs for the ports on the switch indicate  the connection is up and running at 2.5gbps (for the BE25) and 1.0gbps (for the M4/M5).

 

I had a comment from a friend on another forum suggesting that these devices are limited to being daisy-chained (sounds very strange) but I tried that and still no joy - whatever combination of ports/cables (btw all cat6e) they won't both (slave 1/2) show as ethernet backhauled.

 

If I was having interoperability issues between the BEx and Mx , I could understand maybe (different chipset, origins), but in this kindergarten exercise with the three devices in a brandnew network refusing to create the simplest of hub/spoke networks with just 0.5m of Cat7 cable between them and the switch baffles me completely.

 

So I looked to changing to another range (avoiding BE completely) yet the XE75 only offers ONE 2.5gbps port - which also baffles me to understand the use case of when that would suffice (in a FTTH using PPPOE to the ONT) unless you were happy to throttle your backhaul connections to 1gbps. There's no better models out there that offer more than 1 multi gigabit port - so am I stuck - do I have to abort this project with TP Link Deco and start again with another brand? This would be such a shame.

 

Can anyone suggest a model of Deco that supports PPPOE @ 2.5gbps for WAN and has at least 1 extra 2.5gbs port for LAN traffic – AND – is able to backhaul to a switch (which in theory the BE25 should be able to do).


Thanks in advice for any advice.

 

Cheers, Kevin

 

 

  1      
  1      
#1
Options
1 Accepted Solution
Re:BE25 does not support backhaul over switch ??? -Solution
2025-05-15 07:47:02 - last edited 2025-05-15 10:45:54

  @KevinComo : 

 

So, after wasting so much time I've boxed up the 3 BE25s and will send them back to Amazon for a refund. I was naively hoping that someone from TP-Link would see this post and provide some guidance or support on what is going wrong but in the absence of this I'll revert back to my M4/M5 network - simply changing the Router/modem for an Archer BE3600. I know, it's TP-Link and I should maybe think of trying another brand but until I came across these BE25 "toys" I had had a good experience with TP-Link equipment.

 

It's a pity that the Archer provides Wifi 7 but it will be installed in the basement as a simple FTTH Router. Anyway I'll get 2.5Gb on the WAN port and be able to patch the other 2.5Gb port to my office where I can connect with a cable for the PCs.  Only shame is that the rest of the home will have to settle for WiFi 5 mesh (M4/M5) but I think the family will be anyway happy if they can achieve 800mb/s . In the past the bottleneck was always my internet connection (60mb/s) now I have 10gb/s (throttled to 2.5gb/s due to WAN port on the router), so the bottleneck will be the Wifi5 mesh.

 

That said, even if the M4/M5s are only wifi5, at least they can be back hauled using their 1gb/s Ethernet - so they are 100x better than the BE25s tha struggle to achieve even a weak signal through the concrete floors and their lack of back haul capability is astonishing.

 

To close this sorry chapter though, if TP-Link do decide to respond here please could they kindly try to help me understand the following : 

 

Single BE25 running in it's own network in Router mode. Has one port (left/E0) for WAN connected to the ONT. Connects fine over PPPOE at 2.5gb/s.

Connecting via the WiFi to this unit I can achieve good speedtests. My network card is an Intel AX201 160mhz - so doesn't support MLO, but I get a respectable 1.5gb/s 

Connecting my PC via the second (right) Ethernet spare port - using a TP-Link USB/2.5Gb adapter (with the WiFi adapter disabled) - the card negotiates at 2.5gb/s but will not assign a DHCP address to this client !!! Actually, even hard coding the NIC with 192.168.68.10 and gateway 192.168.68.1 (dns 8.8.8.8) , I can't even ping the gateway, let alone access the internet.

 

My question is - what is the point of this second ethernet port if it can't be used for LAN access? If it was there only for back haul purposes why does it not allow my second BE25s to communicate with it on this port? I was tempted to try the X50 but the point Alexandre mentioned about V1/V2 models puts me off since even on the TP-Link website it still states that there is only 1 2.5gbps port Deco X50-PoE | AX3000 Whole Home Mesh WiFi 6 System with PoE | TP-Link Italia - at least here in Italy.

 

The Deco X50 Pro seems (on paper) to be a good option - but I'm scared that I'll find the same issue with the back haul. @TP-Link : Will I have the same problem? 

 

Thanks for any kind of explanation.

 

KR, Kevin

 

 

Recommended Solution
  0  
  0  
#9
Options
12 Reply
Re:BE25 does not support backhaul over switch ???
2025-05-14 11:25:40 - last edited 2025-05-14 11:29:35

  @KevinComo : Only other thought I had was to purchase a dedicated (non-wireless) router with multi gigibit WAN/LAN (such as the TP-Link ER707) but this costs 3x a single BE25. 

 

I realise that in some respects my design could be seen to match the lower of these (since I'm using the master BE25 as my main router).

 

 

Instead, If I were to buy another single BE25 and use that as my PPPOE router (living in its own network) and then setup the new network with 3 of the BE25 running in AP mode,  would that work? Ideally I wouldn't like to downgrade to AP mode (losing all the parental controls and other nice features) - so if my original design should work - I'd persevere down that route.

 

Thanks again!

  0  
  0  
#2
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 12:56:49 - last edited 2025-05-14 12:57:18

  @KevinComo 

 

"My issue is that no matter what I try (different ports/cables etc.) there is no way I can get past the first step, which is to have the BE25s communicate over ethernet backhaul through the TP-Link TL-SG105 switch... the LEDs for the ports on the switch indicate  the connection is up and running at 2.5gbps (for the BE25)."

 

TP-Link TL-SG105 is gigabit switch. It can't have LEDs indicating 2.5Gigabit link.

Are you sure you listed the right switch brand and model?

 

  0  
  0  
#3
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 17:13:32 - last edited 2025-05-14 17:17:46
  0  
  0  
#4
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 17:14:21

  @KevinComo Sorry - I forgot to mention the "-M2"

  0  
  0  
#5
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 20:18:57

  @KevinComo 

 

Right, and I am using same type of switch, just 8-ports: TL-SG108S-M2. Works just fine with my Deco X50-POE. In fact, my Deco didn't like gigabit switch I had previously with my M5/M9 Plus Deco mesh, so I thought your situation is similar to mine I had originally.

 

So, for what I could help you with. If you haven't tried that, try the following: power off everything, including switch and all Decos you have. Unplug everything from the switch except cables that go to Decos. Cables connecting switch to Decos: unplug and plug them back tightly from both ends.

Then, power on Main Deco.

Then, power on switch and see it reports 2.5Gbps link to Main Deco.

Then, power on first Satellite BE25 and see if it uses Ethernet backhaul.

Then, power on second Satellite BE25 and see if it uses Ethernet backhaul.

 

This is very simple setup with just Deco BE25 and switch, nothing else. If that setup works- start powering on rest of your home network device by device and see when it all falls apart.

If you can't get even simple three Deco+switch setup work, I have nothing else I can help you with.

 

--------------------------

 

But, I can also answer your "Can anyone suggest a model of Deco that supports PPPOE @ 2.5gbps for WAN and has at least 1 extra 2.5gbs port for LAN traffic – AND – is able to backhaul to a switch".

 

I am using Deco X50-POE hardware v2, which comes with two 2.5Gbps Ethernet ports and works just fine with the switch of your type, which is master switch at my house.

Note that you should buy X50-POE new from place where their inventory is sold rapidly, such as Amazon. Original X50-POE hardware v1 comes with one 2.5Gigabit and one 1Gigabit Ethernet port. You could only find that by inspecting the box (it lists HW version on label) or by opening it and checking how ports are labeled.

It appears TP-Link quietly replaced v1 with v2, but you might still get v1 from places with stale inventory or previously owned.

 

This is photo of X50-POE hardware v2 Ethernet ports.

 

  1  
  1  
#6
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 21:32:44

  @KevinComo Short Update

 

So it turns out my theory was wrong. Even having 1x BE25 dedicated as a router in its own network , and the other 2x BE25 running in a different network seems not to work

 

1) Factory reset EVERYTHING

2) Power on the first BE25 and create a new network in the Deco App. Connect the WAN cable (from ONT) to port 0, configure as PPPOE and let the setup procedure complete.

3) Connect wirelessly to the new network and run Internet connectivity : success

4) Connect the free ethernet port of the router BE25 to the switch.  Question : I assumed that DHCP should run on both wired and wirelessly connected client but seems not to - why? When I connect my laptop using my TP-link USB3/Ethernet 2.5gbps it negotiates successfully at 2.5gbps but I get no IP address from the BE25. This is why I think the rest fails.

 

5) Power on the second BE25 and create another new network in the Deco App. Configure as DHCP internet and try to complete the procedure but light stays as red and app complains of no internet. having connected the Ethernet0 port to the switch and directly to the router BE25 - no DHCP assigned address and therefore INternet connectivity is provided to the second BE25 which I fully intended to setup as an Access point. Problem is that there's no way to complete the setup - it seems that the BE25s are assumed to have internet connectivity. What if I wanted to use the BE25s in an Intranet environment???

 

So a whole evening wasted. Had to put everything back the way it was working (even if very slowly) and now back to the drawing board. I'm not ready to give up on these BE25s yet, but I'm close. Is it really possible that what I'm trying to do is so difficult that TP-Link doesn't support it? All I want is to have my 3 BE25s communicating at their best speed over ethernet and one of them acting as a master and router with connection to the ONT.

 

Do any TP-Link employees/moderators ever take a look at posts such as these or is it all client/community based help?

 

 

 

 

  0  
  0  
#7
Options
Re:BE25 does not support backhaul over switch ???
2025-05-14 21:48:35 - last edited 2025-05-14 21:50:19

Thanks Alexandre. I was looking at the PX50 Powerline equivalents but they seemed to have just the one ethernet port at 2.5gbps. Actually powerline would work well if connectivity was decent I might not even to use ethernet for the backhaul. The house was recently rewired so cabling is good but I doubt they would reach Theoretical powerline speed of Up to 2,400 Mbps (HomePlug AV2 MIMO standard). More likely to see real-world speed: Typically 300–600 Mbps depending on conditions.

 

The X50 POE models available on Amazon Italy are only single port. I'll have to hunt around for a reseller with the v2 models (unless I take a chance with amazon sending the newer models). The BE25s seem to be really low-spec devices. They're cheap but obviously for a reason. I struggle to understand why they provide 2x 2,5gbps ports if they can't be used in the was I want to use them. Seems a waste.

  0  
  0  
#8
Options
Re:BE25 does not support backhaul over switch ??? -Solution
2025-05-15 07:47:02 - last edited 2025-05-15 10:45:54

  @KevinComo : 

 

So, after wasting so much time I've boxed up the 3 BE25s and will send them back to Amazon for a refund. I was naively hoping that someone from TP-Link would see this post and provide some guidance or support on what is going wrong but in the absence of this I'll revert back to my M4/M5 network - simply changing the Router/modem for an Archer BE3600. I know, it's TP-Link and I should maybe think of trying another brand but until I came across these BE25 "toys" I had had a good experience with TP-Link equipment.

 

It's a pity that the Archer provides Wifi 7 but it will be installed in the basement as a simple FTTH Router. Anyway I'll get 2.5Gb on the WAN port and be able to patch the other 2.5Gb port to my office where I can connect with a cable for the PCs.  Only shame is that the rest of the home will have to settle for WiFi 5 mesh (M4/M5) but I think the family will be anyway happy if they can achieve 800mb/s . In the past the bottleneck was always my internet connection (60mb/s) now I have 10gb/s (throttled to 2.5gb/s due to WAN port on the router), so the bottleneck will be the Wifi5 mesh.

 

That said, even if the M4/M5s are only wifi5, at least they can be back hauled using their 1gb/s Ethernet - so they are 100x better than the BE25s tha struggle to achieve even a weak signal through the concrete floors and their lack of back haul capability is astonishing.

 

To close this sorry chapter though, if TP-Link do decide to respond here please could they kindly try to help me understand the following : 

 

Single BE25 running in it's own network in Router mode. Has one port (left/E0) for WAN connected to the ONT. Connects fine over PPPOE at 2.5gb/s.

Connecting via the WiFi to this unit I can achieve good speedtests. My network card is an Intel AX201 160mhz - so doesn't support MLO, but I get a respectable 1.5gb/s 

Connecting my PC via the second (right) Ethernet spare port - using a TP-Link USB/2.5Gb adapter (with the WiFi adapter disabled) - the card negotiates at 2.5gb/s but will not assign a DHCP address to this client !!! Actually, even hard coding the NIC with 192.168.68.10 and gateway 192.168.68.1 (dns 8.8.8.8) , I can't even ping the gateway, let alone access the internet.

 

My question is - what is the point of this second ethernet port if it can't be used for LAN access? If it was there only for back haul purposes why does it not allow my second BE25s to communicate with it on this port? I was tempted to try the X50 but the point Alexandre mentioned about V1/V2 models puts me off since even on the TP-Link website it still states that there is only 1 2.5gbps port Deco X50-PoE | AX3000 Whole Home Mesh WiFi 6 System with PoE | TP-Link Italia - at least here in Italy.

 

The Deco X50 Pro seems (on paper) to be a good option - but I'm scared that I'll find the same issue with the back haul. @TP-Link : Will I have the same problem? 

 

Thanks for any kind of explanation.

 

KR, Kevin

 

 

Recommended Solution
  0  
  0  
#9
Options
Re:BE25 does not support backhaul over switch ???
2025-05-16 03:56:58

  @KevinComo 

Hi, thank you very much for your feedback.

For your shared topology here:

It should work well when the first BE25 is configured as the PPPOE router and the other two satellite BE25s are supposed to use Ethernet Backhaul, just like the previous Deco M5/M4. And the second Ethernet port on the main Deco BE25 can be used to connect a laptop for internet access.

There is nothing wrong with your configuration based on the description.

(It is not suggested to separate the 3*BE25s by using one as a PPPOE router, then creating a second network with the other two and setting them into Access Point mode)

 

I can't say for sure what caused the failure of the Ethernet Backhaul among Deco BE25s. It seems like something is wrong with its Ethernet port.

 Have you ever tested using another Deco BE25 as the main Deco?

If you'd like to spend a little more time, you can refer to this link to submit APP feedback and attach the APP log, then I can escalate your case to the senior engineer for further assistance: How to submit Deco APP log

 

As the root cause of the Ethernet Backhaul failure on Deco BE25 is still suspended, I can't guarantee Deco X50 Pro will be free of the problem. Theoretically, both Deco BE25 and Deco X50 Pro should be able to establish Ethernet Backhaul.

 

Thank you very much.

Best regards.

  0  
  0  
#10
Options
Re:BE25 does not support backhaul over switch ???
2025-05-16 08:30:34

  @KevinComo 

 

Hi David. Thanks for putting my mind at rest that my design should work. I thought I was going crazy.

 

I have a quick question for you. Is it recommended that the backhaul network is physically segregated from the LAN?

 

I mean, Right now I have an M5 as the master which has one Ethernet going to the Router and another going to the LAN Switch. Many devices are hanging off that LAN.

 

The second and third M5s join the network wirelessly at first but then I attach a cable and connect it again to the LAN Switch.

 

Another question I'd have is on the reliability of the App to show the actually network topology in real-time vs a cached version. I often clos the app and re-open to try to force it to re-discover the network. The browser based tool seems really just there for read-only/view tasks. Is there another browser based admin tool running that I can access the Deco from the PC to configure and monitor the Deco network?


When I attach a cable to the secondary M4/M5s - should the connection update immediately to show wired backhaul? Or it takes a while? Or maybe needs a restart?

 

Thanks again. I'll look at collecting also some logs.

 

Best, Kevin

 

  0  
  0  
#11
Options