@Joseph-TP 

 

Hello,

Thank you for your reply and for taking the time to look into this issue.

Here is the current network topology:

Sophos XG firewall (main router & DHCP server)
—(wired)— Archer BE550 (main unit in Access Point mode)
)))((( Archer BE550 (satellite node in mesh mode)
)))((( Client devices

So the BE550 units are used purely as access points (main + satellite), while routing, NAT, and DHCP are handled by a third-party device (Sophos XG).

Regarding your question about comparison:
Yes, when the BE550 is used as the main router with another BE550 as satellite, the issue does not appear to be noticeable, since the DHCP server is also handled by TP-Link. However, in my current setup, where DHCP is provided by an external firewall/router, the high-frequency DHCP RENEW traffic from the satellite node becomes clearly visible and can impact the DHCP service.

This aligns with your assessment that the satellite router is sending these DHCP requests to confirm its connection with the main router. The behavior is understandable from a mesh connectivity standpoint, but it becomes problematic in more advanced or heterogeneous network environments.

I appreciate that you are willing to escalate this case to your engineers. Please let me know if you need:

• additional logs,

• packet captures,

• or further details about the observed behavior.

I am happy to assist further if it helps improve compatibility and robustness in future firmware versions.

Kind regards,

  @oliiilo 

 

Hi,

 

Just for the record. The behavior you are observing has been reported here previously and it is believed that all models of EasyMesh routers that TP-Link has on offer are like this. Certainly the four different models I have at hand are showing this behavior.
A couple of user posts for example:

https://community.tp-link.com/en/home/forum/topic/832102

https://community.tp-link.com/us/home/threads/topic/727408

 

The same behavior can also be observed when TP-Link's routers are set to "Access Point Mode". In "Access Point Mode" the DHCP renews can be stopped by setting a static IP address on the access point. However, this workaround can't be used for EasyMesh Satellites, because in EasyMesh Satellite mode the routers do not provide a way for the user to set a static IP address.

 

  @woozle 

I'm able to fix the ip of my easymesh node by using mac binding. Whether you can try for this? See the issues still happen?

  @Jasson_Hong 

 

I've the same setup as above mentioned and my BE805 as the easymesh satellite AP. 

 

Tired the static leasing method (mac binding) at my main openwrt router (also the dhcp server) but the BE805 still continues to request for ip address renewal every 30secs. 

 

Hope TP-link can resolves this issue soon or at least provide an option to set static ip in the easymesh satellite to stop this type of unnecessary network noise.

 

Thanks

The same happens to mine, I have three be700 router, which connected by wire, the two satellite router having this lease renew thing every 30 seconds

  @Joseph-TP Sounds good, for the issue I faced with BE700, I've received the two replacement routers so far, and installed the newer firmware (1.2.2 Build 20251027 rel.47412(5553)), but it does not resolve the issue. The main router is behaving normally, it does not renew lease like a crazy person. But the satellite router with that firmware is still behaving like a lunatic and renew lease every 30 sec, even tho I reserved the satellite IP address in main router setup.

 

Also, let me know if they want the backup file and log file to locate the issue. This whole thing is nuts and makes the network barely usable after system run several days.

  @moveingsun 

 

Hi,

 

As I indicated earlier in this thread, that behavior you are seeing on the satellite router is the same for all EasyMesh routers TP-Link makes. There is currently no known fix for it. Replacing routers won't help.
 

@woozle yeah, I get the replacement done before I see this post, I'm specifying that I'm using a new router to just rule out one possible cause.

 

Also, if this is the problem with all Archer routers that perform as satellite router, will it be resolved if I use an Archer router as the main router and non-Archer router as satillite router that is compatible with EasyMesh? To my impression, what you said sounds like this issue has happened since the beginning without a solution.