Hello, I am reporting a bug that occurs at network startup with using the EasyMesh feature with Ethernet backhaul. I will detail the issue below.

Configuration:

• Main router: Archer AX55 V1 (firmware version 1.3.3 Build 20240628 rel.37017(4555)) - Router mode and connected to Ethernet WAN
• Satellite 1: RE330 (connected via Wi-Fi, seems irrelevant but thought I'd mention it either way. Issue occurs with and without it.)
• Satellite 2, main subject of this report: Archer AX10 V1.20 (not V1, V1.20 was not in the list however it uses the same firmware as V1) - firmware 1.3.10 Build 20240130 Rel. 77367 - connected to main AX55 via Ethernet

Expected behaviour:

• Network starts up and the AX10 connects to the AX55 using Ethernet

Actual behaviour & steps to reproduce:

Precondition: AX55 can already be running, or can be turned on at the same time as AX10 (as in the case of a power outage) - the issue is exactly the same

1. AX10 is started. If AX55 isn't already running, it is started too.
2. The network starts up, giving access to the WAN. The AX10 is in an unusable state, with the internet LED flashing red. This lasts for a few minutes, during which the AX10 auto-kicks any device that attempts to connect (causing issues with some devices completely unable to access the network).
3. After a few minutes, the main router (AX55) crashes, with only the power LED staying on.
4. Waiting around 30 minutes (completely impractical) or disconnecting the Ethernet cable to the satellite AX10 fixes the issue.

Temporary workaround:

1. Disconnect the Ethernet cable, boot up the network.
2. All nodes start up, Wi-Fi mesh network is built and is operational. AX10 is at this point using the wireless fallback for EasyMesh.
3. Plug the Ethernet cable back in; mesh now works as intended, with the wireless fallback being disconnected.

Notes:

• I have attempted factory resets of both nodes individually as well as together
• Starting the AX10 after the network is already running causes the same issue (and causes network to stop working) (unless Ethernet cable is disconnected)
• I have tried both the WAN and LAN ports on the satellite AX10 (both are usable for mesh "input"); no difference in behaviour
• I have tried adding the AX10 as a satellite both using the normal method (plug in the Ethernet cable and have it automatically set up) and the wireless method (disconnect cable and add the AX10 like you would add any wireless EasyMesh device)
• The entire network (every device at the same time) restarts at 4 AM every day, having ample time for the issue to go away before anyone tries to use the network.