Archer BE400 AP Mode acting as EasyMesh Controller and BE5000 "sync-server" Restart Loop

Archer BE400 AP Mode acting as EasyMesh Controller and BE5000 "sync-server" Restart Loop

Archer BE400 AP Mode acting as EasyMesh Controller and BE5000 "sync-server" Restart Loop
Archer BE400 AP Mode acting as EasyMesh Controller and BE5000 "sync-server" Restart Loop
Thursday
Model: Archer BE400   Archer BE230  
Hardware Version: V1
Firmware Version: Archer BE400 (V1.0 / Firmware: 1.1.2 Build 20251021),BE5000 (V1.0 / Firmware: 1.1.0 Build 20260108)

Hello, I am experiencing issues with my EasyMesh setup using Wi-Fi 7 routers in Japan.

Note: I selected Archer BE230 for the satellite unit in the model field because Archer BE5000(JP) was not listed, though its specs are similar to the BE230.

 

[My Environment]

  • Main Unit (Controller): Archer BE400(JP) (V1.0 / Firmware: 1.1.2 Build 20251021)

  • Satellite Unit: Archer BE5000(JP) (V1.0 / Firmware: 1.1.0 Build 20260108)

  • Upstream Router: NTT PR-500MI (Required for VoIP/Optical services; functions as DHCP server)

  • Topology: PR-500MI <--(Ethernet)--> BE400(JP) (AP Mode) <--(Wireless)--> BE5000(JP)

 

Issue 1: BE400(JP) acting as EasyMesh Controller in Access Point (AP) Mode

According to the TP-Link FAQ(https://www.tp-link.com/jp/support/faq/3529/), Archer BE400 should not typically function as an EasyMesh Controller in Access Point Mode. However, my BE400(JP) allows me to enable EasyMesh and connect the BE5000(JP) as a satellite while in AP Mode.

  • Initially, when DHCP was set to "Auto," the log showed frequent DHCP renewals every 35 seconds.

  • After switching to a Static IP and disabling the DHCP server manually on the BE400(JP), the logs stabilized.

  • Question: Is it officially supported for the BE400(JP) to act as an EasyMesh Controller in AP Mode? Or is this unintended behavior?

 

Issue 2: BE5000(JP) Satellite Log - "monit restart sync-server" Loop

Regardless of the controller's settings, the satellite BE5000(JP) keeps recording the following logs every minute: 2026-04-13 21:00:01 MONIT Notice [25984] monit restart sync-server 2026-04-13 20:59:01 MONIT Notice [20256] monit restart sync-server

Current Symptoms: Devices near the BE5000(JP) often stay connected to the BE400(JP) (weak signal) instead of roaming. I suspect the "sync-server" loop on the satellite is preventing proper mesh synchronization/steering.

Questions:

  1. Is the BE400(JP)'s behavior in AP Mode considered "normal" for this specific Japanese model?

  2. How can I resolve the "monit restart sync-server" loop on the BE5000(JP)?

I would appreciate any insights or firmware recommendations for these Japan-specific models. Thank you!

  1      
  1      
#1
Options
1 Reply
Re:Archer BE400 AP Mode acting as EasyMesh Controller and BE5000 "sync-server" Restart Loop
Yesterday

Hello @Kazuya_J ,

Welcome to our community.

 

Regarding question 1, this appears to be the response mechanism between the EasyMesh satellite node and the main node. This mechanism should be optimized in the future.

Regarding question 2, it does indeed appear to be an error report.

 

We would like to escalate your case to the support engineers, and they will follow up on it. If you are willing to conduct further analysis, please check your inbox and respond.  

And you can also provide the engineers with more details on your feedback and conduct a thorough discussion.  heart

  0  
  0  
#2
Options