I thought about adding a smart plug to the MOCA power supply adapter and to the ISP gateway and schedule reboots, but I did some troubleshooting early morning today, because it always happens at night, not every night, but every other night, this is the summary:
The AX88U is configured in Dual WAN mode, main WAN is the T-Mobile Sagemcom 5688W, backup WAN is Frontier. Last night something happened that AX88U switch to the backup WAN (Frontier), but it never returned to the main WAN (T-Mobile 5G).
The first thing I did was to disconnect the power from the MOCA device connected to the AX88U, thinking that it could be a MOCA issue, nothing happened, still AX88U connected to the backup WAN. Then disconnected the second MOCA power supply, the one connected close to the Sagemcom 5688W gateway, nothing happened. Then clearly the MOCAs are not causing the problem. The checked the display of the Sagemcom 5688W and everything was fine, signal and connection to the 5G T-Mobile tower. Then I connected a laptop via Ethernet directly to the second ethernet port in the Sagemcom 5688W, and I was able to connect to the internet without any problem, meaning the Sagemcom 5688W gateway was working fine. Then, suddenly the AX88U switched to the main WAN (T-Mobile 5G), it happened just after (30 seconds) I plugged the laptop on the second ethernet port, Sagemcom 5688W connected to the first Ethernet port, super weird, like the first ethernet port was dormant, and got activated when I connected the laptop to the second one.
Here are the logs from the router during the WAN switch event, what are your thoughts from the logs? At some point I think it might be the Dual WAN functioality on the AX88U that is buggy?
Sep 10 02:53:51 rc_service: wanduck 1026:notify_rc restart_wan_if 0
Sep 10 02:53:55 rc_service: wanduck 1026:notify_rc restart_wan_if 1
Sep 10 02:53:56 wan: finish adding multi routes
Sep 10 02:53:57 dhcp client: bound 192.168.12.130/255.255.255.0 via 192.168.12.1 for 86400 seconds.
Sep 10 02:53:57 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Sep 10 02:54:00 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Sep 10 02:54:02 WAN(1) Connection: WAN(1) link up.
Sep 10 02:54:02 rc_service: wanduck 1026:notify_rc restart_wan_if 1
Sep 10 02:54:05 wan: finish adding multi routes
Sep 10 02:54:07 WAN(1) Connection: WAN was restored.
Sep 10 02:54:07 BWDPI: force to flush flowcache entries
Sep 10 02:54:07 BWDPI: rollback fc
Sep 10 02:54:10 kernel: SHN Release Version: 2.0.2 36f59aa
Sep 10 02:54:10 kernel: UDB Core Version: 0.2.20
Sep 10 02:54:10 kernel: sizeof forward pkt param = 280
Sep 10 02:54:10 BWDPI: fun bitmap = 43f
Sep 10 02:54:11 rc_service: udhcpc_wan 16882:notify_rc stop_samba
Sep 10 02:54:11 rc_service: udhcpc_wan 16882:notify_rc start_sambarec
Sep 10 02:54:11 rc_service: waitting "stop_samba" via udhcpc_wan ...
Sep 10 02:54:11 Samba Server: smb daemon is stopped
Sep 10 02:54:12 dhcp client: bound
WWW.ZZZ.YYY.XXX/255.255.255.0 via
WWW.ZZZ.YYY.1 for 1800 seconds.
Sep 10 02:56:10 BWDPI: [BWHIS] Revert process (pid=1434)
Sep 10 08:55:56 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Sep 10 08:56:18 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Sep 10 08:56:21 rc_service: wanduck 1026:notify_rc restart_wan_if 0
Sep 10 08:56:40 wan: finish adding multi routes
Sep 10 08:56:41 dhcp client: bound 192.168.12.130/255.255.255.0 via 192.168.12.1 for 86400 seconds.
Sep 10 09:05:34 rc_service: wanduck 1026:notify_rc restart_wan_line 0
Sep 10 09:05:34 wan: finish adding multi routes
Sep 10 09:05:36 BWDPI: force to flush flowcache entries
Sep 10 09:05:36 BWDPI: rollback fc
Sep 10 09:05:38 kernel: SHN Release Version: 2.0.2 36f59aa
Sep 10 09:05:38 kernel: UDB Core Version: 0.2.20
Sep 10 09:05:38 kernel: sizeof forward pkt param = 280
Sep 10 09:05:38 BWDPI: fun bitmap = 43f
Sep 10 09:05:39 WAN(0) Connection: WAN was restored.
Sep 10 09:05:39 Samba Server: smb daemon is stopped