To the TP-Link Engineering and Product Team,

Background: Following a detailed analysis of the system logs on the Deco BE63, a recurring sequence has been identified that points to a specific optimization opportunity in the error-handling logic between the nrd and apsd processes.

Observed Technical Sequence:

1. Transition Event (Roaming/Band Steering): A wireless client initiates a standard band transition (e.g., 2.4 GHz to 5 GHz). The system attempts to update the WDS table to reflect the change in the device's interface.

    

2. Internal Communication Failure (IOCTL): The Network Resource Daemon (nrd) fails to complete the instruction to the hardware driver to delete the stale entry on the previous interfaces.

    

   • Technical Evidence: qca_delete_wds_entry: failed to send ioctl

      

3. System Response (Global FDB Flush): Due to the inability to perform a surgical update on the MAC address table following the IOCTL failure, the system executes a global fail-safe measure, completely clearing the Forwarding Database (FDB).

    

   • Technical Evidence: ssdk_sh fdb entry flush 1

      

4. Operational Impact: During the period the FDB table is empty, the system must relearn the location of all network devices via packet flooding. This results in perceptible latency and buffering pauses in continuous-stream applications, affecting even devices that were not involved in the initial roaming event.

Engineering Recommendation: It is recommended to review the error-handling sensitivity within the firmware. A failure to delete a specific WDS entry should not ideally result in a global FDB Flush. A more resilient error management approach—isolating the failure to the affected client without impacting the global forwarding database—would significantly enhance stability in high-density device environments.

Best regards,
Nelson Lora