0
Votes

Multi-WAN Implementation on BE900 – Great Feature, But Misaligned with Real Home Office Use

 
0
Votes

Multi-WAN Implementation on BE900 – Great Feature, But Misaligned with Real Home Office Use

Multi-WAN Implementation on BE900 – Great Feature, But Misaligned with Real Home Office Use
Multi-WAN Implementation on BE900 – Great Feature, But Misaligned with Real Home Office Use
22 hours ago
Tags: #EasyMesh Ethernet Backhaul #Multi-WAN Archer BE900
Model: Archer BE900  
Hardware Version: V2
Firmware Version: 1.3.1 Build 20260106

Hello TP-Link Team,

First of all, I want to say that I am a big fan of TP-Link and especially the BE900. The WiFi 7 performance is outstanding, and EasyMesh with my BE800 units works very well in a real home environment.

I invested in this ecosystem because I truly believe in TP-Link’s vision, and I’ve been following your products closely. That’s exactly why I’m taking the time to write this feedback.

The Good: Multi-WAN is a Great Addition

I genuinely appreciate that Multi-WAN has been introduced. This is a very important feature for modern home offices and prosumer setups.

For example, a realistic scenario today is:

              •            Primary ISP: 4 Gbps fiber

              •            Secondary ISP: 2 Gbps fiber (failover / load balancing)

This is not an extreme enterprise case — this is already happening in real homes.

So yes: Multi-WAN is absolutely the right direction, and I applaud TP-Link for adding it.

The Problem: Current Implementation Breaks the Network Architecture

However, the current implementation creates a major issue:

Multi-WAN is limited to the two 10G ports only, while the four 2.5G ports remain LAN-only with no option to assign WAN.

This forces the user to:

              1.           Use one 10G port for WAN 1

              2.           Use the second 10G port for WAN 2

              3.           Connect the internal network (switch, NAS, backhaul) through a 2.5G LAN port

Why This Is a Problem

This design effectively creates a bottleneck:

              The entire internal network becomes limited to 2.5 Gbps

              The 10G LAN backbone is lost

              NAS transfers, backups, and internal traffic are degraded

              The main advantage of owning a 10G-capable router is reduced

In simple terms:

To use Multi-WAN, we are forced to sacrifice the 10G LAN backbone — which is exactly why many of us bought the BE900 in the first place.

What Would Make Sense (Real-World Design)

A much more logical and practical implementation would be:

              •            Primary WAN (4 Gbps) → 10G port

              •            Secondary WAN (2 Gbps) → one dedicated 2.5G port (configurable as WAN)

              •            Keep the second 10G port → LAN backbone to switch/NAS/backhaul

This allows:

              •            Load balancing and failover

              •            Full use of 10G LAN

              •            No unnecessary bottlenecks

Key Point

No user — beginner or advanced — wants to sacrifice a 10G LAN trunk just to enable Multi-WAN.

The current implementation unintentionally penalizes the exact users who invest in high-end infrastructure.

Suggestion

Please consider:

              Allowing at least one 2.5G port to be configurable as WAN

              Or introducing a dedicated 2.5G WAN option via firmware

This would make Multi-WAN truly usable in real home and prosumer environments.Final Thought

The BE900 hardware is excellent.

The direction is right.

But the current Multi-WAN implementation limits its real-world potential.

I hope this feedback helps improve an already great product.

Thank you.

#1
Options