Disable rebuilding EasyMesh network when Ethernet backhaul is used
Hello :) My network is instable - EasyMesh keeps rebuilding, despite having constant, stable Ethernet backhaul. Can I (and how do I) disable WiFi EasyMesh when using Ethernet backhaul?
Thanks in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Not sure you can do this because Easymesh falls back to a wireless backhaul when the wired backhaul is down for some reason.
- Copy Link
- Report Inappropriate Content
Hi all and thanks to all of you for support.
TL;DR: when using Easymesh, Ethernet backhaul should be connected 1:1 between the router and the satellite; In my situation (router - switch - satellites), access points with the same WiFi SSID was what I needed.
Details:
My network infrastructure looks like this: modem -> main router -> switch -> extenders.
Modem is supplied by my ISP, but this element doesn't affect any LAN networking whatsoever. Switch is TL-SG108E, extenders are AX23s.
In the beginning of this story the main router was AR5344 supplied by my ISP. It's kind of advanced-looking device, with graphical topology (which lied most of the times regarding connection type; for example, my wife's S22 was mostly seen as LAN device instead of WiFi).
Using this device, I have succesfully configured Easymesh... Kind of. 2.4GHz WiFi speed was astonishing 15-20Mbps. 5G was better, reaching up to 200-250Mbps. But that's not what I paid for! I pay for 600 and I'll use 600! Also, the network kept disconnecting, Easymesh was constantly being rebuilt and finally it settled down on linear configuration (router -> satellite -> satellite), which also caused network devices to connect to improper WiFi points.
So at this moment I created this topic. I assumed that something was wrong with Easymesh constantly rebuilding the network using WiFi, when Ethernet backhaul was available. Oh boy, how wrong was I.
I replaced the router from ISP with another AX23. I configured Easymesh, plugged my living room extender with Eth backhaul, works perfectly. Plugged second one the same way, located on the other side of home and BOOM! Main router kept rebooting, I had little to no stability. Ping in LAN went nuts, even DHCP had problems assigning proper IP addresses...
And from what I have read, Ethernet backhaul is only supported in 1 to 1 connection. Therefore, it looks like I misunderstood the topic of multipoint WiFi.
In the beginning of this network, I have used two WR820N routers and I named their WiFis like "ISP_NAME_LivingRoom" or "ISP_NAME_someting", but I have never used the same SSID. My understanding was, that if I name my WiFi networks with the same SSIDs, I'd struggle to determine which one is which, and I'd still have to manually change networks when moving through the house. As you might expect, I was wrong about this one. I'm able to move my laptop at home and the network change is pretty seamless.
Now it works with one satellite, I'll try the second one tomorrow. EDIT: Yup, it works. At least I learned something. Once again, thanks for all the comments.
- Copy Link
- Report Inappropriate Content
Not sure you can do this because Easymesh falls back to a wireless backhaul when the wired backhaul is down for some reason.
- Copy Link
- Report Inappropriate Content
Hi @Szczepan94
For your case, please also try the following suggestions:
1. Verify that both the main router and satellite devices support EasyMesh Ethernet Backhaul and have the latest Ethernet Backhaul-supported firmware.
2. Follow the correct configuration process outlined in the guide for building an Ethernet backhaul using two EasyMesh routers: Build an Ethernet Backhaul
3. Check the Ethernet cable between the main router and satellite device and try using different cables.
4. If there is a switch or other devices in between, connect the satellite device directly to the main router.
5. Try using different Ethernet/LAN ports on the main router and satellite devices as the backhaul port.
6. Reset the satellite device and repeat the EasyMesh configuration process.
- Copy Link
- Report Inappropriate Content
@Joseph-TP thanks, but these are like the most generic troubleshooting steps. My network works okay, I have full stability and transfers through LAN, all devices support EasyMesh with Ethernet backhaul. Everything works fine, but I have limited transfer on some of my devices and stability of the connection is bad.
Let me rephrase the question: is there any way of diagnosing EasyMesh networks? Like some debug application for it? I can't access configuration page, since it's not available when TP-Link device is a sattelite and I can't see anything useful on my main router.
- Copy Link
- Report Inappropriate Content
Hi @Szczepan94
Can I know which specific clients are unstable? Is the unstable connection mainly manifested in wireless connection or wired connection? What are the specific manifestations? Are these devices mainly connected to the satellite router?
There are several potential reasons and troubleshooting steps you can take:
1. Check Wi-Fi signal strength: Ensure that the affected client devices are within range of the TP-Link router and not obstructed by obstacles. Consider repositioning the router or using Wi-Fi range extenders to improve coverage.
2. Adjust wireless channel: Change the wireless channel on the router to minimize interference from neighboring networks.
3. Check wired connections: If the affected devices are wired, try using different Ethernet cables and ports to rule out any issues with the connections.
4. Update client device drivers: Make sure the network adapter drivers on the affected client devices are up to date.
5. Disable router features: Temporarily disable advanced router features like Quality of Service (QoS) that may be causing compatibility issues with specific client devices.
6. Update router firmware: Check for and install any available firmware updates for the TP-Link router to address compatibility issues and improve stability.
- Copy Link
- Report Inappropriate Content
Hi all and thanks to all of you for support.
TL;DR: when using Easymesh, Ethernet backhaul should be connected 1:1 between the router and the satellite; In my situation (router - switch - satellites), access points with the same WiFi SSID was what I needed.
Details:
My network infrastructure looks like this: modem -> main router -> switch -> extenders.
Modem is supplied by my ISP, but this element doesn't affect any LAN networking whatsoever. Switch is TL-SG108E, extenders are AX23s.
In the beginning of this story the main router was AR5344 supplied by my ISP. It's kind of advanced-looking device, with graphical topology (which lied most of the times regarding connection type; for example, my wife's S22 was mostly seen as LAN device instead of WiFi).
Using this device, I have succesfully configured Easymesh... Kind of. 2.4GHz WiFi speed was astonishing 15-20Mbps. 5G was better, reaching up to 200-250Mbps. But that's not what I paid for! I pay for 600 and I'll use 600! Also, the network kept disconnecting, Easymesh was constantly being rebuilt and finally it settled down on linear configuration (router -> satellite -> satellite), which also caused network devices to connect to improper WiFi points.
So at this moment I created this topic. I assumed that something was wrong with Easymesh constantly rebuilding the network using WiFi, when Ethernet backhaul was available. Oh boy, how wrong was I.
I replaced the router from ISP with another AX23. I configured Easymesh, plugged my living room extender with Eth backhaul, works perfectly. Plugged second one the same way, located on the other side of home and BOOM! Main router kept rebooting, I had little to no stability. Ping in LAN went nuts, even DHCP had problems assigning proper IP addresses...
And from what I have read, Ethernet backhaul is only supported in 1 to 1 connection. Therefore, it looks like I misunderstood the topic of multipoint WiFi.
In the beginning of this network, I have used two WR820N routers and I named their WiFis like "ISP_NAME_LivingRoom" or "ISP_NAME_someting", but I have never used the same SSID. My understanding was, that if I name my WiFi networks with the same SSIDs, I'd struggle to determine which one is which, and I'd still have to manually change networks when moving through the house. As you might expect, I was wrong about this one. I'm able to move my laptop at home and the network change is pretty seamless.
Now it works with one satellite, I'll try the second one tomorrow. EDIT: Yup, it works. At least I learned something. Once again, thanks for all the comments.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 220
Replies: 5
Voters 0
No one has voted for it yet.