AX53 going into "Not Reachable" mode EasyMesh Ethernet backhaula
Hello, I have an EasyMesh network with an AX55 V1 as the main router, and an RE190 and AX53 V1 as satellites. The AX53 is connected via Ethernet backhaul to the AX55. At random moments (every 2-3 days), the AX53 goes into a "not reachable" mode, where it cannot be accessed via the Tether app or web interface, and the "internet" LED on the device itself is off. The router remains in this state until a reboot; reconnecting the Ethernet cable doesn't change anything.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @lisukup
I'm happy to inform you that the official firmware of Archer AX53 V1 will be rolled out gradually in various regions soon and we would like to provide a pre-release version for you to enjoy new features like EasyMesh Ethernet Backhaul, IoT Network, WireGuard VPN, etc.
Give it a go and let me know how it works in your network:
Archer AX53 V1 Supports EasyMesh Ethernet Backhaul, WireGuard VPN, IoT Network, and More
- Copy Link
- Report Inappropriate Content
Hi @lisukup
May I know if your network topology diagram is as follows:
AX55—router )))((( client devices
(Note: — stands for wired connection,)))((( stands for wireless connection)
- Follow the correct configuration process outlined in the guide for building an Ethernet backhaul using two EasyMesh routers: How to Build an Ethernet Backhaul Using Two EasyMesh Routers
- Check the Ethernet cable between the main router and satellite device and try using different cables.
- If there is a switch or other devices in between, connect the satellite device directly to the main router, bypass the switch.
- Try using different Ethernet/LAN ports on the main router and satellite devices as the backhaul port.
- Reset the satellite device and repeat the EasyMesh configuration process.
- Copy Link
- Report Inappropriate Content
(Satellite) Repeater RE190 )))((( AX55 (Main Router) ------ AX53 Satellite
On the same cable, there was an IP Camera working before, directly connected to the main router (about 9 meters). Now I have changed the location of the AX53 to another place, with another ethernet cable plugged in, through a simple gigabit switch. I reset the AX53 without success. The only thing I didn't change until now was the port on the main router. Now it's connected to a different port using a different cable.
The OneMesh did not reconnect through WiFi after the fault; it looked like the AX53 was dead.
@edit
before the Reset, i had multiple Offline satelits in my network (in Tether app), only with a random MAC listed
- Copy Link
- Report Inappropriate Content
Hi @lisukup ,
Do you mean there is a switch between the main router and satellite router? Did you try to remove the switch and connect the satellite router directly to the main router? Because we need to determine if the problem is with the switch?
In addition, what is the model of your switch?
- Copy Link
- Report Inappropriate Content
@lisukup
It was not connected before through a switch.
Now i connected it through a switch only to try another LAN port of the main router.
After 2 days i have the same issue.
The swtich model - LS1005G
- Copy Link
- Report Inappropriate Content
According to your detailed description, it seems the AX53 freezes. Can you please confirm the below?
Connect a PC to one of AX53's LAN ports when the internet LED is off on it and it goes into a "not reachable" mode, then check if the PC can receive a valid IP address from the network.
BTW, please reset the AX53 one more time and follow this guide to connect it back to the network, then check again if the connectivity will be stable.
- Copy Link
- Report Inappropriate Content
@Kevin_Z
The situation now:
The AX53 is connected to another port on the main router directly, using a different cable than on the begining.
My laptop is connected to the lan port of the Ax53.
The AX53 is "not reachable", but the LAN ports are working normal (the AX53 ist workin now as a lan switch), i get a valid IP adress, the connection on LAN is working normal.
I did the reset - now i need to wait a few days.
- Copy Link
- Report Inappropriate Content
@Kevin_Z after all, i get again the "Not Reachable" mode / state.
I did the reset and connected the AX53 to the network like in the guide.
In addition, i have 220 "other mesh devices" in my network
- Copy Link
- Report Inappropriate Content
Apologies as I am running out of solutions on where to locate the exact file.
To assist and figure it out efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up. Thank you.
- Copy Link
- Report Inappropriate Content
Hello @lisukup
I'm happy to inform you that the official firmware of Archer AX53 V1 will be rolled out gradually in various regions soon and we would like to provide a pre-release version for you to enjoy new features like EasyMesh Ethernet Backhaul, IoT Network, WireGuard VPN, etc.
Give it a go and let me know how it works in your network:
Archer AX53 V1 Supports EasyMesh Ethernet Backhaul, WireGuard VPN, IoT Network, and More
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 196
Replies: 9
Voters 0
No one has voted for it yet.