@Stuu 

Wireless backhaul to the nodes is a must! The "eeeeaaaassyyy" way is to add the feature to lock the mac address of the upstream device (so it doesn't jump to the main router).... COME ON ALREADY TP-LINK  

@Solla-topee @Sunshine @Joseph-TP @Clive_A 
Hi everyone,

It’s been over 2 years since I first opened this thread asking TP-Link to support daisy chaining OneMesh extenders — where one extender connects wirelessly to another, instead of being forced to connect only to the main router.

Since then, the thread has grown into a community-wide request with dozens of replies, 20+ votes, and users sharing the same frustration:

• OneMesh extenders default back to the main router, even when a nearby extender has stronger signal
• This results in dropped connections, underused devices, and a mesh system behaving like a star topology
• Many of us were drawn in by the promise of “mesh”, only to discover this key feature is missing
• Workarounds like Ethernet or Powerline defeat the purpose of going wireless

What are we asking for?

• Add the ability to lock onto a specific upstream MAC address instead of just SSID
• Enable true wireless daisy chaining with smart routing based on signal strength
• Prioritize reliability over theoretical speed – which is what most users need

Some clever users have tried removing extenders from OneMesh, blocking MACs, or relying on non-mesh fallback setups — but all of these are temporary hacks. We need an official solution.

TP-Link reps @Solla-topee  and @Sunshine:

We’ve heard “future consideration” for a long time. Can we please get a real update or roadmap? This is clearly a highly requested feature with practical impact.

To all reading this: please vote at the top of the thread if you haven’t already. Let’s keep the pressure on!

Thanks to everyone who shared their setups and ideas.

– Modude

+1 trying to extend between buildings so I need a true mesh that can repeat the network to reach these far distances

@Joseph-TP @Solla-topee @Sunshine @Clive_A

Hi @Joseph-TP , thank you for the detailed reply.

It’s good to hear that system-level optimization is underway, but the core issue still remains unresolved for many of us. This thread goes back to 2022 and includes voices from dozens of users who purchased OneMesh products expecting mesh-like behavior — specifically wireless daisy chaining between extenders — not just connections directly to the router.

You mentioned that “mainstream manufacturers generally use SSID-level relay logic.” However, Deco (your own product line), as well as mesh systems from Eero, ASUS AiMesh, and Google Nest WiFi, all support wireless extender chaining or at least intelligent routing between nodes — which is what users expect when they hear the term “mesh.”

As for MAC-level control, products like Ubiquiti’s UniFi and ASUS routers allow advanced configuration and client steering logic that achieves similar results. Even if MAC locking isn’t feasible now, allowing extenders to favor stronger signals over defaulting to the main router would be a huge step forward.

We’re not just asking for edge-case tinkering — this is a core function that affects usability in larger homes and multi-floor setups. TP-Link markets OneMesh as a mesh solution, but current behavior aligns more with a star topology. The difference is real, and it’s affecting user trust.

Thanks again, and I hope you’ll keep this feature request alive — it’s clearly important to the community.

- Modude

  @Modude 

Modude wrote

@Clive_A

Hi Joseph-TP , thank you for the detailed reply.

 

It’s good to hear that system-level optimization is underway, but the core issue still remains unresolved for many of us. This thread goes back to 2022 and includes voices from dozens of users who purchased OneMesh products expecting mesh-like behavior — specifically wireless daisy chaining between extenders — not just connections directly to the router.

 

You mentioned that “mainstream manufacturers generally use SSID-level relay logic.” However, Deco (your own product line), as well as mesh systems from Eero, ASUS AiMesh, and Google Nest WiFi, all support wireless extender chaining or at least intelligent routing between nodes — which is what users expect when they hear the term “mesh.”

As for MAC-level control, products like Ubiquiti’s UniFi and ASUS routers allow advanced configuration and client steering logic that achieves similar results. Even if MAC locking isn’t feasible now, allowing extenders to favor stronger signals over defaulting to the main router would be a huge step forward.

We’re not just asking for edge-case tinkering — this is a core function that affects usability in larger homes and multi-floor setups. TP-Link markets OneMesh as a mesh solution, but current behavior aligns more with a star topology. The difference is real, and it’s affecting user trust.

Thanks again, and I hope you’ll keep this feature request alive — it’s clearly important to the community.

- Modude

I am not a home team member. Your action and remark make zero sense to me. Do not randomly @ community members, as this appears to be a spam action. Please watch out your action and read the community guidelines. 

Modude is very clearly articulating what many customers expect from a system that is marketed as a mesh but it actually doesn't provide core mesh functionality. I don't see any spam like activity here. This is the kind of email you would see at work when someone is trying to get attention on a technical shortcoming and the issue isn't getting the attention it deserves from the right people. Just my 2 cents.

It does seem there's a disconnect with the tplink reps that respond to this forum vs engineers and program managers who are actually involved with the product. If this is not the product that can provide mesh network functionality and you are steering people toward the Deco product then say that. To call it a mesh when it is not a mesh leads to the kind of frustration that boils over in this thread because the expectations were not properly set.

To reply rudely and threateningly to customers who are politely and articulately making a valid point that's just bad customer service. Hopefully future customers can read this thread and find out that OneMesh is not actually a mesh or understand this while they are still able to return the product and buy another product like Eero instead.

@Clive_A not spam. Thought u work for TP-Link. Only @you cuz u replied to the thread early on. Wont @you again. Bye now. 
 

@Tubedr thanks 🫶🏻

  @Modude 

Modude wrote

@Clive_A not spam. Thought u work for TP-Link. Only @you cuz u replied to the thread early on. Wont @you again. Bye now. 
 

@Tubedr thanks 🫶🏻

Unfortunately, that's not true. I am not responsible for the home products. And I did not engage in this thread. You must be mistaken.

Now, you will need to wait for the related page admin or moderator to reply. 

Down the road, if you need to find the related admin or moderator, browse through the posts, and you'll see their names and mention them if you need help.