WAN was exceptionally disconnected

[cipsius]

Joined to say that turning off network monitoring via ping worked for me too, to resolve exactly this problem that was happening extremely often. So pleased I saw your post! I switched to monitoring via DNS lookup and that doesn’t cause the same problem for me no disconnects for days. Running 386_45934 on an AX82U, and using AiMesh.

I as well joined just to say thank you and confirm also this work around.
I would have WAN disconnections, "WAN Connection: WAN was exceptionally disconnected", every other day or even daily. After switching to "DNS Query" &"DNS probe", for the last 8 days all is stable.
In my troubleshooting, AI Mesh netw AX86U (v.386_46061)+ RP-AX56 (v.386_42860), even the ISP ONT was exchanged and traces running on their interface and side, to no use. Undetermined reasons for WAN disconnection.

Seems there is a deep laying bug in the software when AiMesh is active and PING probing.

Same router without AiMesh active, same ISP provider but different ONT, would not determine this WAN fail.

Thank you again and hope this will resolved in a future FW upgrade.

 

[Lynx]

If these issues are related to the same problem I had, namely absence of timely udhcpc release/renew on NO-CARRIER events, then this script may fix the problem:

GitHub - lynxthecat/maintain-wan-lease: Resolve problem with Asus Merlin routers in terms of release/renew of udhcpc.

Resolve problem with Asus Merlin routers in terms of release/renew of udhcpc. - lynxthecat/maintain-wan-lease

github.com