@Joseph-TP @Sunshine  I am writing this to express my deep dissatisfaction with the current state of the Archer BE230 v1.20 and the lack of a professional solution regarding the 1.2.5 firmware issues.

The stability issues with MLO and IPv6 are well-documented in this community (Threads #862218 and #862230). It is clear that this is a widespread software regression and not an isolated configuration error. Since the update, my network has become unreliable, defeating the purpose of upgrading to a Wi-Fi 7 system.

Furthermore, the suggestion to downgrade to firmware 1.2.1 is completely unacceptable. We are talking about software that is 9 months old. Asking users to revert to a nearly year-old version means:

1. Losing critical security patches released in the last several months.

2. Sacrificing performance optimizations: Previous versions suffered from significant Wi-Fi slowness, an issue that had been gradually improving with recent updates. Downgrading would force me back to those poor speeds and poor performance.

3. Accepting a broken product instead of receiving the modern support we paid for.

I did not purchase a flagship Wi-Fi 7 router to run outdated, slow software just because your engineering team failed to stabilize the current build.

I am requesting the following:

• An immediate Beta firmware that addresses the 1.2.5 instability issues without forcing us back to the 'stone age' of version 1.2.1.

• A transparent timeline for the next official stable release.

• An escalation of this case to the senior engineering team.

If TP-Link cannot provide a functional, up-to-date firmware for this hardware revision, I will have no choice but to pursue a full refund through consumer protection authorities, as the product fails to meet its advertised specifications.

Hello @Joseph-TP 

The TP-Link Archer BE230 router previously experienced frequent IPv6 disconnections regardless of the configuration. However, stability has significantly improved after enabling "Respond to Pings from WAN" and "Get IP using Unicast DHCP." For users on the Megacable ISP, these settings appear to be key for a reliable connection.

Additionally, during preliminary testing of the MLO (Multi-Link Operation) feature with a POCO F7, the network appears more stable. That said, MLO performance has not yet been thoroughly evaluated over an extended period.

Technical Questions:

1. Is it strictly necessary to keep "Respond to Pings from WAN" and "Unicast DHCP" active, or could these settings introduce potential security or performance issues?

2. Are there any plans for a firmware version 1.3.x in the near future?