BE88U + BE58U AiMesh — complete WiFi failure

[curiouscookie]

Been dealing with random complete WiFi outages on my BE88U (Merlin 3006.102.7) — all clients drop at once, nothing can reconnect, only a reboot fixes it. Dug into the syslog and found eth1 (2.5G wired backhaul to my BE58U node) flapping constantly with some SerDes PHY errors mixed in. Also seeing WLCSCBDEAUTHENTICATEFORREASON err -30 storms and ACSD chanim query failed -16 right before every mass drop.

Rolled back the BE58U from the March 11 Asus stock firmware to the previous version and everything stabilized immediately — no drops, no flapping since.

Has anyone else seen backhaul instability after the BE58U March 11 update with the BE88U running Merlin 3006.102.7? Curious if this is isolated to my setup or wider. Also wondering if the BE88U's behavior under backhaul stress — dropping every client catastrophically instead of degrading gracefully — is a known Broadcom driver issue.

Happy to share the syslog if useful.

 

[jksmurf]

Not able to comment on your specific issue but your example makes me wonder sometimes (as RMerlin doesn’t use AiMesh himself**) whilst each unit works perfectly well in isolation (one having Merlin FW and one Stock FW) whether the Stock FW node has had much by way of testing with an older FW-based Main Route.

The GPL in 3006.102.7 e.g. is likely a bit older than the one on your node, with its various enhancements and fixes. The only thing I can suggest is you factory reset and re-add the recently updated RT-BE58U node, if you haven’t already done so. Won’t lose much if it’s stock anyway, worth a try?

** Unfortunately RMerlin has stated his apartment is too small for AIMesh, we need to get him out onto a sprawling estate so he can test AIMesh and tell Asus what a disaster it is, until his toes turn blue…