What's new

AX88U Merlin 386.x and 388.1 random WAN disconnects mostly without relevant log entries

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

JohnDeere

Regular Contributor
Hello everyone,

I have a WAN disconnection problem since 386.x and 388.1. If anyone has any idea, please let me know. The symptom is:

Dec 05 18:29:23 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 05 18:29:28 RT-AX88U WAN(0)_Connection WAN was restored.

My WAN connection gets disconnected randomly. There are days when no disconnection occurs at all. And there are days when WAN is disconnected a dozen of times.

This problem is present with dual WAN on and also when it's off.
I tried turning off AI protection, QoS too, but WAN still not stable.
I tried to play with dual WAN settings, tried many test domains, but nothing really solved random WAN disconnection.
I have an external Mikrotik modem which provides the WAN connection with WAN IP pass-through. I always check the modem's log, but there are no modem WAN interruptions at all. The modem log is clean, no errors.

I have amtm installed and running with Diversion and Skynet updated. I tried turning off some and all of these, but seemed to have no effect on WAN disconnections.

Sometimes I can "force" the disconnection to occur if I download very large files. I've just did this. I downloaded a 1GB test file without problems, and when I tried to download the 10GB test file, WAN suddenly disconnected.

Dec 05 18:52:06 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 05 18:52:41 RT-AX88U WAN(0)_Connection WAN was restored.

After reconnection it starts downloading the 10GB test file... then at 2.3GB suddenly WAN disconnects again...

Next attempt on 3.8GB more disconnects happen. This time the upcoming log entries might be relevant:
Dec 05 19:17:04 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 05 19:17:25 RT-AX88U WAN(0)_Connection WAN was restored.
Dec 05 19:18:06 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 05 19:18:06 RT-AX88U WAN(0)_Connection WAN was restored.
Dec 05 19:19:05 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 05 19:19:47 RT-AX88U rc_service wanduck 1034:notify_rc restart_wan_if 0
Dec 05 19:19:47 RT-AX88U custom_script Running /jffs/scripts/service-event (args: restart wan_if)
Dec 05 19:19:47 RT-AX88U ovpn-server1 event_wait : Interrupted system call (code=4)
Dec 05 19:19:47 RT-AX88U ovpn-server1 Closing TUN/TAP interface
Dec 05 19:19:47 RT-AX88U ovpn-server1 /usr/sbin/ip addr del dev tun21 10.8.0.1/24
Dec 05 19:19:47 RT-AX88U lldpd removal request for address of 10.8.0.1%39, but no knowledge of it
Dec 05 19:19:47 RT-AX88U ovpn-server1 ovpn-down 1 server tun21 1500 1621 10.8.0.1 255.255.255.0 init
Dec 05 19:19:47 RT-AX88U ovpn-server1 PLUGIN_CLOSE: /usr/lib/openvpn-plugin-auth-pam.so
Dec 05 19:19:47 RT-AX88U ovpn-server1 PLUGIN AUTH-PAM: Error signaling background process to exit: Connection refused (errno=111)
Dec 05 19:19:47 RT-AX88U ovpn-server1 SIGTERM[hard,] received, process exiting
Dec 05 19:19:47 RT-AX88U ovpn-server2 event_wait : Interrupted system call (code=4)
Dec 05 19:19:47 RT-AX88U ovpn-server2 Closing TUN/TAP interface
Dec 05 19:19:47 RT-AX88U ovpn-server2 /usr/sbin/ip addr del dev tun22 10.16.0.1/24
Dec 05 19:19:47 RT-AX88U lldpd removal request for address of 10.16.0.1%40, but no knowledge of it
Dec 05 19:19:47 RT-AX88U ovpn-server2 ovpn-down 2 server tun22 1500 1621 10.16.0.1 255.255.255.0 init
Dec 05 19:19:47 RT-AX88U ovpn-server2 PLUGIN_CLOSE: /usr/lib/openvpn-plugin-auth-pam.so
Dec 05 19:19:47 RT-AX88U ovpn-server2 PLUGIN AUTH-PAM: Error signaling background process to exit: Connection refused (errno=111)
Dec 05 19:19:47 RT-AX88U ovpn-server2 SIGTERM[hard,] received, process exiting
Dec 05 19:19:47 RT-AX88U lldpd removal request for address of 37.xxx.57.142%12, but no knowledge of it
Dec 05 19:19:50 RT-AX88U wan finish adding multi routes
...



Anyone any idea please?
Thanks :)
 
Change "Log only messages more urgent than" to "all" on System Log - General Log. See if that yields any more information the next time the problem occurs.
 
Thanks for your reply. I already have it set to all
1670268229731.png
 
I would also recommend tapping into your broadband modem log as well... I had a similar problem, and it ended up being an Xfinity problem upstream from our neighborhood that was causing all the disconnects. Being able to provide them with "definitive proof" through logs like these that it was their issue, and not my own "equipment" issue, was invaluable.
 
Im trying to troubleshoot disconnects and ping spikes, seems to be approx every 20 mins. AX86U, 388.1.
Code:
05/12/2022 8:23:47 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:23:48 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:23:49 PM - Reply from 8.8.8.8: bytes=32 time=22ms TTL=117
05/12/2022 8:23:50 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:51 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:23:52 PM - Reply from 8.8.8.8: bytes=32 time=20ms TTL=117
05/12/2022 8:23:53 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:55 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:56 PM - Reply from 8.8.8.8: bytes=32 time=22ms TTL=117
05/12/2022 8:23:57 PM - Reply from 8.8.8.8: bytes=32 time=38ms TTL=117
05/12/2022 8:23:58 PM - Reply from 8.8.8.8: bytes=32 time=36ms TTL=117
05/12/2022 8:23:59 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:00 PM - Reply from 8.8.8.8: bytes=32 time=38ms TTL=117
05/12/2022 8:24:01 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:24:02 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:03 PM - Reply from 8.8.8.8: bytes=32 time=29ms TTL=117
05/12/2022 8:24:04 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:05 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:24:06 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:24:07 PM - Reply from 8.8.8.8: bytes=32 time=56ms TTL=117
05/12/2022 8:24:08 PM - Reply from 8.8.8.8: bytes=32 time=309ms TTL=117
05/12/2022 8:24:09 PM - Reply from 8.8.8.8: bytes=32 time=576ms TTL=117
05/12/2022 8:24:10 PM - Reply from 8.8.8.8: bytes=32 time=637ms TTL=117
05/12/2022 8:24:14 PM - Request timed out.
05/12/2022 8:24:16 PM - Reply from 8.8.8.8: bytes=32 time=460ms TTL=117
05/12/2022 8:24:17 PM - Reply from 8.8.8.8: bytes=32 time=477ms TTL=117
05/12/2022 8:24:18 PM - Reply from 8.8.8.8: bytes=32 time=381ms TTL=117
05/12/2022 8:24:22 PM - Request timed out.
05/12/2022 8:24:24 PM - Reply from 8.8.8.8: bytes=32 time=337ms TTL=117
05/12/2022 8:24:25 PM - Reply from 8.8.8.8: bytes=32 time=467ms TTL=117
05/12/2022 8:24:26 PM - Reply from 8.8.8.8: bytes=32 time=444ms TTL=117
05/12/2022 8:24:27 PM - Reply from 8.8.8.8: bytes=32 time=339ms TTL=117
05/12/2022 8:24:31 PM - Request timed out.
05/12/2022 8:24:33 PM - Reply from 8.8.8.8: bytes=32 time=426ms TTL=117
05/12/2022 8:24:34 PM - Reply from 8.8.8.8: bytes=32 time=265ms TTL=117
05/12/2022 8:24:34 PM - Reply from 8.8.8.8: bytes=32 time=214ms TTL=117
05/12/2022 8:24:36 PM - Reply from 8.8.8.8: bytes=32 time=631ms TTL=117
05/12/2022 8:24:36 PM - Reply from 8.8.8.8: bytes=32 time=198ms TTL=117
05/12/2022 8:24:37 PM - Reply from 8.8.8.8: bytes=32 time=98ms TTL=117
05/12/2022 8:24:39 PM - Reply from 8.8.8.8: bytes=32 time=582ms TTL=117
05/12/2022 8:24:40 PM - Reply from 8.8.8.8: bytes=32 time=255ms TTL=117
05/12/2022 8:24:41 PM - Reply from 8.8.8.8: bytes=32 time=317ms TTL=117
05/12/2022 8:24:42 PM - Reply from 8.8.8.8: bytes=32 time=385ms TTL=117
05/12/2022 8:24:43 PM - Reply from 8.8.8.8: bytes=32 time=347ms TTL=117
05/12/2022 8:24:44 PM - Reply from 8.8.8.8: bytes=32 time=539ms TTL=117
05/12/2022 8:24:45 PM - Reply from 8.8.8.8: bytes=32 time=317ms TTL=117
05/12/2022 8:24:46 PM - Reply from 8.8.8.8: bytes=32 time=225ms TTL=117
05/12/2022 8:24:46 PM - Reply from 8.8.8.8: bytes=32 time=55ms TTL=117
05/12/2022 8:24:47 PM - Reply from 8.8.8.8: bytes=32 time=72ms TTL=117
05/12/2022 8:24:48 PM - Reply from 8.8.8.8: bytes=32 time=32ms TTL=117
05/12/2022 8:24:50 PM - Reply from 8.8.8.8: bytes=32 time=501ms TTL=117
05/12/2022 8:24:51 PM - Reply from 8.8.8.8: bytes=32 time=160ms TTL=117
05/12/2022 8:24:52 PM - Reply from 8.8.8.8: bytes=32 time=118ms TTL=117
05/12/2022 8:24:52 PM - Reply from 8.8.8.8: bytes=32 time=78ms TTL=117
05/12/2022 8:24:54 PM - Reply from 8.8.8.8: bytes=32 time=127ms TTL=117
05/12/2022 8:24:55 PM - Reply from 8.8.8.8: bytes=32 time=100ms TTL=117
05/12/2022 8:24:56 PM - Reply from 8.8.8.8: bytes=32 time=537ms TTL=117
05/12/2022 8:24:57 PM - Reply from 8.8.8.8: bytes=32 time=216ms TTL=117
05/12/2022 8:24:58 PM - Reply from 8.8.8.8: bytes=32 time=521ms TTL=117
05/12/2022 8:24:59 PM - Reply from 8.8.8.8: bytes=32 time=442ms TTL=117
05/12/2022 8:25:00 PM - Reply from 8.8.8.8: bytes=32 time=384ms TTL=117
05/12/2022 8:25:04 PM - Request timed out.
05/12/2022 8:25:06 PM - Reply from 8.8.8.8: bytes=32 time=566ms TTL=117
05/12/2022 8:25:06 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:07 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:25:08 PM - Reply from 8.8.8.8: bytes=32 time=30ms TTL=117
05/12/2022 8:25:09 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:10 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:11 PM - Reply from 8.8.8.8: bytes=32 time=20ms TTL=117
05/12/2022 8:25:12 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:13 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:14 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:15 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:25:16 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:17 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:18 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:19 PM - Reply from 8.8.8.8: bytes=32 time=21ms TTL=117
05/12/2022 8:25:20 PM - Reply from 8.8.8.8: bytes=32 time=21ms TTL=117
05/12/2022 8:25:21 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:22 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117

Watching pings that's how it looks, I've got logs set to debug and all but nothing showing there. Did a full wipe going from beta 3 to 4 as I had the same issue, new on official release.
 
Im trying to troubleshoot disconnects and ping spikes, seems to be approx every 20 mins. AX86U, 388.1.
Code:
05/12/2022 8:23:47 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:23:48 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:23:49 PM - Reply from 8.8.8.8: bytes=32 time=22ms TTL=117
05/12/2022 8:23:50 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:51 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:23:52 PM - Reply from 8.8.8.8: bytes=32 time=20ms TTL=117
05/12/2022 8:23:53 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:55 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:23:56 PM - Reply from 8.8.8.8: bytes=32 time=22ms TTL=117
05/12/2022 8:23:57 PM - Reply from 8.8.8.8: bytes=32 time=38ms TTL=117
05/12/2022 8:23:58 PM - Reply from 8.8.8.8: bytes=32 time=36ms TTL=117
05/12/2022 8:23:59 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:00 PM - Reply from 8.8.8.8: bytes=32 time=38ms TTL=117
05/12/2022 8:24:01 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:24:02 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:03 PM - Reply from 8.8.8.8: bytes=32 time=29ms TTL=117
05/12/2022 8:24:04 PM - Reply from 8.8.8.8: bytes=32 time=26ms TTL=117
05/12/2022 8:24:05 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:24:06 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:24:07 PM - Reply from 8.8.8.8: bytes=32 time=56ms TTL=117
05/12/2022 8:24:08 PM - Reply from 8.8.8.8: bytes=32 time=309ms TTL=117
05/12/2022 8:24:09 PM - Reply from 8.8.8.8: bytes=32 time=576ms TTL=117
05/12/2022 8:24:10 PM - Reply from 8.8.8.8: bytes=32 time=637ms TTL=117
05/12/2022 8:24:14 PM - Request timed out.
05/12/2022 8:24:16 PM - Reply from 8.8.8.8: bytes=32 time=460ms TTL=117
05/12/2022 8:24:17 PM - Reply from 8.8.8.8: bytes=32 time=477ms TTL=117
05/12/2022 8:24:18 PM - Reply from 8.8.8.8: bytes=32 time=381ms TTL=117
05/12/2022 8:24:22 PM - Request timed out.
05/12/2022 8:24:24 PM - Reply from 8.8.8.8: bytes=32 time=337ms TTL=117
05/12/2022 8:24:25 PM - Reply from 8.8.8.8: bytes=32 time=467ms TTL=117
05/12/2022 8:24:26 PM - Reply from 8.8.8.8: bytes=32 time=444ms TTL=117
05/12/2022 8:24:27 PM - Reply from 8.8.8.8: bytes=32 time=339ms TTL=117
05/12/2022 8:24:31 PM - Request timed out.
05/12/2022 8:24:33 PM - Reply from 8.8.8.8: bytes=32 time=426ms TTL=117
05/12/2022 8:24:34 PM - Reply from 8.8.8.8: bytes=32 time=265ms TTL=117
05/12/2022 8:24:34 PM - Reply from 8.8.8.8: bytes=32 time=214ms TTL=117
05/12/2022 8:24:36 PM - Reply from 8.8.8.8: bytes=32 time=631ms TTL=117
05/12/2022 8:24:36 PM - Reply from 8.8.8.8: bytes=32 time=198ms TTL=117
05/12/2022 8:24:37 PM - Reply from 8.8.8.8: bytes=32 time=98ms TTL=117
05/12/2022 8:24:39 PM - Reply from 8.8.8.8: bytes=32 time=582ms TTL=117
05/12/2022 8:24:40 PM - Reply from 8.8.8.8: bytes=32 time=255ms TTL=117
05/12/2022 8:24:41 PM - Reply from 8.8.8.8: bytes=32 time=317ms TTL=117
05/12/2022 8:24:42 PM - Reply from 8.8.8.8: bytes=32 time=385ms TTL=117
05/12/2022 8:24:43 PM - Reply from 8.8.8.8: bytes=32 time=347ms TTL=117
05/12/2022 8:24:44 PM - Reply from 8.8.8.8: bytes=32 time=539ms TTL=117
05/12/2022 8:24:45 PM - Reply from 8.8.8.8: bytes=32 time=317ms TTL=117
05/12/2022 8:24:46 PM - Reply from 8.8.8.8: bytes=32 time=225ms TTL=117
05/12/2022 8:24:46 PM - Reply from 8.8.8.8: bytes=32 time=55ms TTL=117
05/12/2022 8:24:47 PM - Reply from 8.8.8.8: bytes=32 time=72ms TTL=117
05/12/2022 8:24:48 PM - Reply from 8.8.8.8: bytes=32 time=32ms TTL=117
05/12/2022 8:24:50 PM - Reply from 8.8.8.8: bytes=32 time=501ms TTL=117
05/12/2022 8:24:51 PM - Reply from 8.8.8.8: bytes=32 time=160ms TTL=117
05/12/2022 8:24:52 PM - Reply from 8.8.8.8: bytes=32 time=118ms TTL=117
05/12/2022 8:24:52 PM - Reply from 8.8.8.8: bytes=32 time=78ms TTL=117
05/12/2022 8:24:54 PM - Reply from 8.8.8.8: bytes=32 time=127ms TTL=117
05/12/2022 8:24:55 PM - Reply from 8.8.8.8: bytes=32 time=100ms TTL=117
05/12/2022 8:24:56 PM - Reply from 8.8.8.8: bytes=32 time=537ms TTL=117
05/12/2022 8:24:57 PM - Reply from 8.8.8.8: bytes=32 time=216ms TTL=117
05/12/2022 8:24:58 PM - Reply from 8.8.8.8: bytes=32 time=521ms TTL=117
05/12/2022 8:24:59 PM - Reply from 8.8.8.8: bytes=32 time=442ms TTL=117
05/12/2022 8:25:00 PM - Reply from 8.8.8.8: bytes=32 time=384ms TTL=117
05/12/2022 8:25:04 PM - Request timed out.
05/12/2022 8:25:06 PM - Reply from 8.8.8.8: bytes=32 time=566ms TTL=117
05/12/2022 8:25:06 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:07 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:25:08 PM - Reply from 8.8.8.8: bytes=32 time=30ms TTL=117
05/12/2022 8:25:09 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:10 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:11 PM - Reply from 8.8.8.8: bytes=32 time=20ms TTL=117
05/12/2022 8:25:12 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:13 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:14 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:15 PM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=117
05/12/2022 8:25:16 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:17 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117
05/12/2022 8:25:18 PM - Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
05/12/2022 8:25:19 PM - Reply from 8.8.8.8: bytes=32 time=21ms TTL=117
05/12/2022 8:25:20 PM - Reply from 8.8.8.8: bytes=32 time=21ms TTL=117
05/12/2022 8:25:21 PM - Reply from 8.8.8.8: bytes=32 time=27ms TTL=117
05/12/2022 8:25:22 PM - Reply from 8.8.8.8: bytes=32 time=24ms TTL=117

Watching pings that's how it looks, I've got logs set to debug and all but nothing showing there. Did a full wipe going from beta 3 to 4 as I had the same issue, new on official release.
What kind of bandwidth do you have? Do you have any bandwidth-hungry apps, services or people on your end possibly sapping all remaining bandwidth? Or is this continuous every 20mins / 24hrs per day?
 
What kind of bandwidth do you have? Do you have any bandwidth-hungry apps, services or people on your end possibly sapping all remaining bandwidth? Or is this continuous every 20mins / 24hrs per day?
25Mb/s up 250Mb/s down. I've tried with and without Adguard (installed via AMTM), with and without entware (usb3 stick). with QOS (cake/adaptive - with manual setting) and without. QOS should prevent data cutting out all together I would think so don't think its that. Ive tried with and without ddns set. Gonna try openvpn disabled shortly to see how that goes. DOS protection didnt seem to stop it.

Also Ive been aware of it for about a week, been busy with work so not had so much time to sit and figure it out.
 
25Mb/s up 250Mb/s down. I've tried with and without Adguard (installed via AMTM), with and without entware (usb3 stick). with QOS (cake/adaptive - with manual setting) and without. QOS should prevent data cutting out all together I would think so don't think its that. Ive tried with and without ddns set. Gonna try openvpn disabled shortly to see how that goes. DOS protection didnt seem to stop it.

Also Ive been aware of it for about a week, been busy with work so not had so much time to sit and figure it out.
Certainly annoying. Is it causing any lags/delays in your browsing or streaming shows?

Are you seeing any wonkyness with tests like these? https://speed.cloudflare.com/
 
Certainly annoying. Is it causing any lags/delays in your browsing or streaming shows?

Are you seeing any wonkyness with tests like these? https://speed.cloudflare.com/
yes first noticed as my son plays FPS games (as do I friday nights) massive ping spikes/disconnects. Streaming goes low res/pixelated. streamed radio disconnects etc.

Really weird it is, rebooted router 9.08, it happened on schedule at 9.30.

More info, also have an ac68u, currently as meshed node (tried with it in AP mode same issue).

Gonna run round the house check all physical connections :)
 
yes first noticed as my son plays FPS games (as do I friday nights) massive ping spikes/disconnects. Streaming goes low res/pixelated. streamed radio disconnects etc.

Really weird it is, rebooted router 9.08, it happened on schedule at 9.30.

More info, also have an ac68u, currently as meshed node (tried with it in AP mode same issue).

Gonna run round the house check all physical connections :)
Think Im gonna have to put my ISP (Virgin media UK Hub 3) modem back into router mode for a few days as im guessing its that and see if I can see anything in the the logs while I run ping test. Thanks for https://speed.cloudflare.com/ handy that is, running slower than usual which is why I think its an ISP thing.
 
I would also recommend tapping into your broadband modem log as well... I had a similar problem, and it ended up being an Xfinity problem upstream from our neighborhood that was causing all the disconnects. Being able to provide them with "definitive proof" through logs like these that it was their issue, and not my own "equipment" issue, was invaluable.
Thank you for your reply. I checked my modem log, but the LTE modem log is perfectly clean. The modem's ethernet log shows some diconnections, but not as many as in AX88U. And not in the same time.
Sometimes disconnections occur when a VPN client connects to the AX88U VPN server. But not each time...
I just can't find anything that can be related to this annoying problem.
 
Thank you for your reply. I checked my modem log, but the LTE modem log is perfectly clean. The modem's ethernet log shows some diconnections, but not as many as in AX88U. And not in the same time.
Sometimes disconnections occur when a VPN client connects to the AX88U VPN server. But not each time...
I just can't find anything that can be related to this annoying problem.
I know it's probably a longshot, but how about replacing the cable that runs between your modem and router? Have an extra one you can try?
 
I had a couple of weeks ago the same problem.
For me in connection with VPN.
Had a few post over it in de vpnmon thread.

Just WAN(0) link down and WAN(0) link restored sometimes within a second, no further log.
And then my vpn connected devices became WAN connected devices, while the killswitch was on.
Glad not to live in China or N-Korea
Just re-installed clean new, did replace all cables and hallelujah, it was working since, without the vpn/wan connection problems.
Still I'm not sure where problem came from.

Except had had a week ago the "wan red light problem" (no wan possible constant red WAN light)
After search on the web I discovered I was not the only one.
Was almost prepared to dump the ASUS router (AX68) in the bin (2 months old)
But after 3!! re-flashes, the red light became white again.

Sure, its my problem, just waiting on the next problem.
Not convinced about the ASUS hardware/software router combination.
 
I know it's probably a longshot, but how about replacing the cable that runs between your modem and router? Have an extra one you can try?
I've already replaced the cable before, but with the same type, same manufacturer. This time I've replaced the WAN cable with a double shielded SFTP cable. Now I'm monitoring the log to see if there's any difference.
 
My problem is exactly the same. Disconnect - reconnect sometimes within a few seconds. Exactly the same as yours. Without any relevant log entry.
This has just happened while I'm writing:

Dec 07 18:05:16 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 07 18:05:17 RT-AX88U WAN(0)_Connection WAN was restored.
Dec 07 18:06:22 RT-AX88U WAN(0)_Connection WAN(0) link down.
Dec 07 18:06:37 RT-AX88U WAN(0)_Connection WAN was restored.
Dec 07 18:08:43 RT-AX88U WAN(0)_Connection WAN(0) link down.

There are days when there's no disconnection at all and I hope the problem is gone. Then something happens and it starts disconnecting again.
This time it began after I upgraded to the latest 388.1

I admit I did some "dirty upgrades" with the latest versions. I really wanted to avoid resetting the router again because of so many settings... but seems like I will have to do it anyway. If this was the solution for you, it may be a solution for me too.
Thanks for your post :)

I also get this warning on every ovpn connection. I thought it may have some relation with disconnections.

Dec 07 14:34:28 RT-AX88U ovpn-server1 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1601', remote='link-mtu 1585'
 
If this is over an LTE connection trying lowering the WAN MTU to something like 1300 or 1400.
Thanks for the reply. I set MTU to 1400 both in modem and AX88U WAN settings, but the the situation became a lot worse. Even impossible to download a 1GB test file. I'm not sure the MTU setting did this though... I set it back to 1500 and still worse than before. However ovpn log still gives me this warning Wed Dec 7 19:37:11 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1585', remote='link-mtu 1601' not sure if has anything to do with WAN MTU setting...
 
Thanks for the reply. I set MTU to 1400 both in modem and AX88U WAN settings, but the the situation became a lot worse
The idea is to set the router's WAN MTU to be lower than that of the modem. So if the modem defaults to 1500, set the router to 1400.
 
Thanks for the reply. I set MTU to 1400 both in modem and AX88U WAN settings, but the the situation became a lot worse. Even impossible to download a 1GB test file. I'm not sure the MTU setting did this though... I set it back to 1500 and still worse than before. However ovpn log still gives me this warning Wed Dec 7 19:37:11 2022 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1585', remote='link-mtu 1601' not sure if has anything to do with WAN MTU setting...
I didn't even pick up on that you're using an LTE modem until @ColinTaylor mentioned this. I'm going to have to guess that a wireless signal like this will always run into more connection issues than a hardline. Here are a few more plausible explanations in your case for why you see it working most times, but not other times:

1. Cell tower is overloaded/latency issues
2. Wireless interference from some other outside source
3. Signal quality or low signal issues
4. Electromagnetic interference / sunspots. ;)
 
using an LTE modem
There are many, many staples that hold the whole thing together.
Networking is not for average Joe, I'm afraid.
To many points can fail solo or in cascade.

But consumer products are made for average Joe (maybe I'm wrong)
My original problem had the same effects, but no LTE modem.
My connection to the internet is a 1,5mtr long CAT7 cable.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top