New Release EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller
Exciting news!
We're thrilled to announce the rollout of new official firmware rolling out for multiple routers, including the BE, AX, and AC series, which introduces EasyMesh in AP Mode as a Controller. We invite you to upgrade and install this latest firmware version to try it out.
This Article Applies to:
Model & Hardware & Firmware | Update Date |
---|---|
Archer BE11000 Pro(US)_V1.6_1.1.0 Build 20240730 and newer versions | Sep 2, 2024 |
Archer BE700 Pro(US)_V1.6_1.1.0 Build 20240730 and newer versions | Sep 2, 2024 |
Archer BE550 Pro_V1&V1.6_1.1.0 Build 20240730 and newer versions | Sep 2, 2024 |
Archer BE3600_V1_1.1.0 Build 20240729 and newer versions | Sep 2, 2024 |
Archer BE230_V1&V1.6_1.1.0 Build 20240729 and newer versions | Sep 2, 2024 |
Archer AX55(EN)_V1_1.3.3 Build 20240628 and newer versions | Sep 2, 2024 |
Archer AX55(US/CA/TW)_V1_1.3.2 Build 20240325 and newer versions | Sep 2, 2024 |
Archer C80_V2.20/V2.26_1.14.0 Build 240617 and newer versions | Sep 2, 2024 |
Archer C6_V4_1.14.0 Build 240617 and newer versions | Sep 2, 2024 |
Archer C86_V1_1.14.0 Build 240617 and newer versions | Sep 2, 2024 |
Archer A8_V2.20/V2.26_1.14.0 Build 240617 and newer versions | Sep 2, 2024 |
Moderator Note:
1. The availability of EasyMesh in AP Mode may vary by region even for the same model. Please check your local website for more information.
2. The above list might not include all models and hardware versions. It is recommended to keep watching the firmware releases for your router, as all the newly supported features will be listed in the patch notes if/when it is added to your version.
User Scenarios:
Some users would prefer to, or are limited by their devices to, have their main modem router acting as the gateway and DHCP server in the network, which requires using the TP-Link Wi-Fi router in AP (Access Point) Mode to avoid the double-NAT issue. However, they also wish to utilize the EasyMesh feature of the TP-Link Wi-Fi router to create a mesh network with other EasyMesh routers or extenders.
The topology is roughly as follows (Topo 1):
Or as this one (Topo 2):
Note: In this topo, both the EasyMesh Wi-Fi router and the satellite router/extender must support EasyMesh Ethernet Backhaul.
You may also connect the EasyMesh Wi-Fi routers like below, it will also work (Topo 3):
Note: In this topo, the EasyMesh Wi-Fi router and the satellite router/extender must also support EasyMesh Ethernet Backhaul.
Comment below if you have any feedback or run into any issues — we’re here to help.
Related Articles:
[Wi-Fi Routers] AP Mode supports EasyMesh
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Kevin_Z After changing the Wi-Fi power setting from "high" to "medium", both satellites are now succesfully working with Ethernet Backhaul!
I've had a couple of instances of one of the satellites dropping out from the EasyMesh network, however I'm not sure if that may have been due to the fact that I enabled STP on my router's LAN interface recently, due to constant kernel error messages stating "received packet on [interface] with own address as source address".
I've since disabled STP on that interface, as I read that it can interfere with the hand-off of clients that occurs with EasyMesh. Fingers crossed that fixes the issue.
Overall, I'd say that when it's working fully (i.e without any issues), the experience with EasyMesh is very good.
The hand-off between the different APs isn't instaneous (it seems to take 4-5 seconds after you go from one room to another before it hops to the new AP), however it is completely seamless (i.e the connection never drops, as it would with regular separate APs). I get at least 150-200Mbps no matter where I am in the house, which substantially increases when I'm closer to an AP.
I'm generally very happy with the result so far.
- Copy Link
- Report Inappropriate Content
I have a problem with connecting the easy mesh repeater via ethernet
maybe I also need to disable stp on the gateway and check the installation again
in my configuration the role of gateway and dhcp server is performed by a third-party router
there are 2 pieces tp link archer c6 v4
with this beta firmware I got the following results:
c6 operating mode - router mode, easy mesh - main router, lan gateway-lan c6 connection, dhcp disabled, static ip assigned in the desired subnet - always works stably
c6 satellite router, easy mesh connection via ethernet to wan port - works unstably, disconnects, the controller shows only ethernet connection
c6 satellite router, easy mesh connection via ethernet to lan port - works unstably, disconnects, the controller shows either ethernet connection or wifi
for fun, I even tried to put one c6 into access point mode by connecting an ethernet cable from the lan gateway to the c6 wan port, but even without easy mesh I got disconnects on the access point
- Copy Link
- Report Inappropriate Content
@Godlike66 You say you have a third-party router acting as the gateway and DHCP server? So the Archer C6s are simply meant to act as wireless access points, with seamless roaming using EasyMesh?
If that's the case, you need to choose one of the C6s to act as the EasyMesh Controller and put it in Access Point operating mode:
Once it reboots into Access Point Mode, if it supports acting as an EasyMesh Controller in AP mode, you should then see EasyMesh as an option in the Advanced settings tab:
Enable EasyMesh if it isn't enabled already and make sure Current Mode is set to "Main Router" (confusing terminology, unfortunately). Now you can add the other C6s to the EasyMesh network, by changing the EasyMesh mode setting in their configuration page from "Main Router" to "Satellite Router" - this will cause them to reboot, at which point you should go back to the configuration page for the Controller C6 and click the "Add" button, to add the newly discoverable satellite APs to the EasyMesh Network.
As was mentioned previously, when you add the satellite routers, you should make sure to connect them to the LAN via their LAN port, rather than the WAN port. I was actually still able to set it up without doing this, however it's probably best practice to follow their recommended setup.
- Copy Link
- Report Inappropriate Content
t4n0n wrote
@Kevin_Z After changing the Wi-Fi power setting from "high" to "medium", both satellites are now succesfully working with Ethernet Backhaul!
I've had a couple of instances of one of the satellites dropping out from the EasyMesh network, however I'm not sure if that may have been due to the fact that I enabled STP on my router's LAN interface recently, due to constant kernel error messages stating "received packet on [interface] with own address as source address".
I've since disabled STP on that interface, as I read that it can interfere with the hand-off of clients that occurs with EasyMesh. Fingers crossed that fixes the issue.
Overall, I'd say that when it's working fully (i.e without any issues), the experience with EasyMesh is very good.
The hand-off between the different APs isn't instaneous (it seems to take 4-5 seconds after you go from one room to another before it hops to the new AP), however it is completely seamless (i.e the connection never drops, as it would with regular separate APs). I get at least 150-200Mbps no matter where I am in the house, which substantially increases when I'm closer to an AP.
I'm generally very happy with the result so far.
Thank you very much for your valuable feedback. I'm happy to hear that you resolved it by modifying the Transmit Power on the main AX55. Very good try.
It seems that the wireless signal strength is sufficient for a connection when the Transmit Power is set to High. However, in EasyMesh scenarios, the system automatically prefers Ethernet backhaul over wireless when an Ethernet cable is present between the nodes. In your case, it might be the switch affecting this behavior.
Could you please tell me the brand and model number of the switch? You may leave the STP off on the switch and monitor the connectivity for a week or two.
- Copy Link
- Report Inappropriate Content
Hello, maybe you know when will be available that option for Archer BE550v1?
- Copy Link
- Report Inappropriate Content
-You say you have a third-party router acting as the gateway and DHCP server? So the Archer C6s are simply meant to act as wireless access points, with seamless roaming using EasyMesh?
Yes, that's right.
-If that's the case, you need to choose one of the C6s to act as the EasyMesh Controller and put it in Access Point operating mode:
understand, I know and understand all this perfectly well)
if it were that simple in my case, I wouldn't write such long posts here)
just to assess my literacy, I have configured omada with vlan more than once, I understand such simple things as setting up easy mesh perfectly
and it worked when tp link was a gateway
p.s.
disabling stp on the gateway by the way did not affect the improvement of performance
as soon as I put even one c6 in access point mode, I see continuous disconnects
- Copy Link
- Report Inappropriate Content
please check in your lab the functionality of this firmware, as well as other firmware for the archer c6 v4 router
router mode - access point
and also easy mesh in the mode when the main gateway and dhcp server is not a tp link router
maybe it works with other routers, but not with this model
as soon as I put even one C6 into access point mode, the network starts to drop
and for some reason the access point turns on its own dhcp server
this is what happens if the router c6 is in access point mode, the ethernet cable from the gateway is connected to the wan port of C6, and I am connected from the computer with an ethernet cable to C6 (192.168.2.1 - gateway)
however, if I disconnect the cable between C6 and the gateway, then reboot C6, it turns out that it has its own dhcp server running on the same subnet as the gateway.
screenshot also from a computer connected to C6 with an ethernet cable to a lan port
as you can see, router C6, being in access point mode, which in theory should not distribute addresses, is a gateway with its own dhcp server in fact, although there are no such settings, but I can easily access this router
I can also easily get an address from this router in access point mode if I connect to wifi from my phone
at the same time, if I do not connect the public network cable to the C6 router, but simply configure the C6 tplink in access point mode, then it will change its default dhcp server from 192.168.0.1 to 192.168.0.254 and will broadcast addresses in its subnet, which initially contradicts the access point, which should not broadcast addresses, but only receive the address of the main gateway
exactly the same story happens when adding a satellite to easy mesh
I configure the first Archer C6, disable dhcp on it and give it an IP address in the subnet I need
after which I add a satellite to the easy mesh router, which reboots into access point mode, a third-party gateway and a dhcp server assigns it an IP address, I see it with this IP address and in the easy mesh list.
but if I connect this satellite router to the computer separately from all others, then it will also distribute dhcp addresses. and access to it will be via the ip address that was assigned to it by the main gateway and dhcp server.
That's how things are.
a similar problem is apparently relevant not only with this beta firmware, but also with the latest release for archer C6 v4
because even with the release firmware I saw problems, although I didn't analyze them so thoroughly
- Copy Link
- Report Inappropriate Content
I am attaching screenshots of the log from the gateway
and also with archer c6 in access point mode at the moment when the problem appears
- Copy Link
- Report Inappropriate Content
To analyze your issue in detail, I would need your detailed network layout as well as all the models of the devices in this network, including the gateway router or switches.
- Copy Link
- Report Inappropriate Content
this problem is relevant not only for beta firmware, but also for the final resolution for Archer C6 V4 (Archer C6(RU)_V4_1.13.6 Build 240430)
Also, a similar problem was observed in another case with the release firmware 1.13.6 Build 240430, when the main gateway and dhcp server was Speedster (KN-3010) EU with firmware 4.2.1, the satellite router behaved exactly the same
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 7175
Replies: 64