BE550v1 - Bugs, Errors, problems & other issues

BE550v1 - Bugs, Errors, problems & other issues

34 Reply
Re:BE550v1 - Bugs, Errors, problems & other issues
2024-09-08 02:16:41

  @ChrisBS after updating to 1.0.11 firmware I still having issues with BE550 losing connection constantly 2.4/5/6 band.

  0  
  0  
#32
Options
Re:BE550v1 - Bugs, Errors, problems & other issues-Solution
2025-01-16 13:01:02 - last edited 2025-01-16 13:03:10

@ChrisBS  @GabrielR112 

 

I'm updating the status of the new official firmware of the BE550 V1 and hope others can also install it to confirm if the overall performance will be improved.

 

The official version 1.1.1 Build 20241230 brings a range of improvements and new features to enhance your networking experience, offering better performance, security, and ease of use. This update is gradually rolling out, and users can check for updates on the BE550's web interface or through the Tether App and install the latest version. We strongly recommend upgrading to this version to improve the overall experience.

 

Check the following thread to get more details:

[Official Release] Archer BE550 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, ECO Mode, and More

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Introducing AI QoS: Elevate Your Gaming Experience on the Archer GE800 Gaming Router! Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
Recommended Solution
  0  
  0  
#33
Options
Re:BE550v1 - Bugs, Errors, problems & other issues
2025-06-26 16:34:06
When am on a video call the WiFi drops I am the latest firmware
  0  
  0  
#34
Options
Re:BE550v1 - Bugs, Errors, problems & other issues
Monday

  @ChrisBS 

 

Summary

When an Archer BE550 is used as a mesh satellite node (wireless backhaul), its DHCP client enters an abnormal renewal loop, sending DHCP RENEW requests every ~30–40 seconds despite receiving a long lease time (several days).

This behavior can overload or destabilize some DHCP servers and is not compliant with normal DHCP client behavior.

Observed Behavior

  • The mesh node successfully receives a DHCP lease with a long duration (≈ 7 days).

  • Immediately after receiving the ACK, the node logs:

    “1/2 lease passed, enter renewing state”

  • The node then renews the lease repeatedly every ~30–40 seconds.

  • This loop continues indefinitely.

Expected Behavior

  • DHCP renewal should occur at T1 ≈ 50% of lease time, not immediately.

  • With a multi-day lease, renewals should happen after several days, not seconds.

Key Evidence (from device logs)

Example pattern observed repeatedly:


 

receive ack from server with lease ≈ 600000 seconds 1/2 lease passed, enter renewing state send renew request

This indicates that the DHCP client miscalculates the lease timer.

Scope of the Issue

  • Occurs only on the mesh satellite node

  • The main BE550 (root node) does not show this behavior

  • Occurs with:

    • Wireless mesh backhaul (Wi-Fi 6/6E/7)

    • Smart Connect enabled or disabled

    • MLO enabled or disabled

  • The issue persists even with:

    • Fixed channels

    • Reduced channel width

    • Long DHCP lease times

Workarounds Tested

  • Using a static IP on the main node stops the issue for that device.

  • Mesh satellite nodes cannot keep a static IP (settings are overridden in mesh mode).

  • DHCP reservation on the server side keeps the IP stable but does not stop the renew loop.

  • Changing Wi-Fi performance settings may reduce frequency but does not fully fix the issue.

Impact

  • Excessive DHCP traffic

  • Potential DHCP service instability on some routers/firewalls

  • Difficult to diagnose unless DHCP logs are inspected

  • Affects advanced network setups more severely

Conclusion

This appears to be a firmware bug in the DHCP client implementation of the Archer BE550 mesh satellite node, where the lease timer is incorrectly evaluated, causing immediate renewal loops.

A firmware fix is recommended to correct DHCP lease timing logic in mesh mode.

  0  
  0  
#35
Options