@Eddie_G_Kibel 

Dear members,

I kept waiting for a while for the firmware versions to be released, hoping AX53 oficial firmware would be re-released taking into consideration Ethernet Backhaul.

Since it hasn't happened for a while, I decided to move forward.

1) I upgraded my AX72 tot he current firmware version (1.2.6 Build 20240619 rel.72016(5553))

Note 1: that I have a CAT6 network cable running from AX72 LAN ports 1 and 2 directly to each AX53 (I have 2 AX53).

Note 2: I currently have my AX53s running firmware BETA version ax53v1-up-us-ver1-2-4-P1[20240206-rel41393]-1024_nosign_2024-02-06_14.05.03 (which supports Ethernet Backhaul).

2) I did, as a colleague here in this forum posted, factory reset my AX53 (#1). Once the process was complete, finally I had nothing to do. AX72 automatically found my AX53 via network cable, and automatically added him via Ethernet Backhaul to the EasyMesh network! It takes a few minutes (I'd say 3-6) - so be patient - as it adds the router to the easymesh, and then does the IP address change, and then changes from Wireless to Ethernet connection. So give it some minutes (3-6) to complete the process. Incredibly simple now! Once AX53 #1 process was complete, I did the same to AX53 #2. Same as described here in item 2, all went smooth. It seems finally TP-Link got the grip of it! KUDOS!

Last 2 tries I did it was chaos - first time my AX72 had a previous firmware version, and second time I used AX53 firmware ax53v1-up-us-ver1-2-4-P1[20240206-rel41393]-1024_nosign_2024-02-06_14.05.03 (only to find out later it did not support Ethernet Backhaul!) - so I rolled back my AX53s to the Beta version.

I've just setup beta firmware to AX53 and set up easy mesh with C80 router. They are connected via CAT7 cable. I can see C80 as wired mesh device in the mesh client list. Wired devices in the network that's connected to C80 can utilize the full bandwidth towards rest of the wired network, through AX53.

However, WiFi sufers with high jitter. I'm literally next to the C80. Below is the ping output to the C80 IP address

PING 192.168.0.25 (192.168.0.25): 56 data bytes                                                                                         │
64 bytes from 192.168.0.25: icmp_seq=0 ttl=64 time=3.438 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=1 ttl=64 time=2.178 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=2 ttl=64 time=2.190 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=3 ttl=64 time=3.579 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=4 ttl=64 time=178.687 ms                                                                           │
64 bytes from 192.168.0.25: icmp_seq=5 ttl=64 time=90.223 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=6 ttl=64 time=134.534 ms                                                                           │
64 bytes from 192.168.0.25: icmp_seq=7 ttl=64 time=1.711 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=8 ttl=64 time=50.999 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=9 ttl=64 time=1.830 ms                                                                             │
64 bytes from 192.168.0.25: icmp_seq=10 ttl=64 time=137.477 ms                                                                          │
64 bytes from 192.168.0.25: icmp_seq=11 ttl=64 time=6.658 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=12 ttl=64 time=5.143 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=13 ttl=64 time=96.832 ms                                                                           │
64 bytes from 192.168.0.25: icmp_seq=14 ttl=64 time=2.494 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=15 ttl=64 time=7.598 ms                                                                            │
64 bytes from 192.168.0.25: icmp_seq=16 ttl=64 time=55.249 ms                                                                           │
64 bytes from 192.168.0.25: icmp_seq=17 ttl=64 time=103.880 ms                                                                          │
^C                                                                                                                                      │
--- 192.168.0.25 ping statistics ---                                                                                                    │
18 packets transmitted, 18 packets received, 0.0% packet loss                                                                           │
round-trip min/avg/max/stddev = 1.711/49.150/178.687/57.533 ms

Pinging the main router AX53 is not very much different.

64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=71.565 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=11.799 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=62.943 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.696 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=2.915 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=32.450 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=84.348 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 31 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.417/26.953/114.138/34.698 ms

My speed tests via iperf3 shows 250mbps - 350 mbps range.

Before this, I did not enable mesh and was just using same SSID in both devices. I don't have my previous data at hand but I was easily seeing 600mbps in this floor, yet alone being next to the router.

What went wrong here?