What's new
  • 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!

WAN Drops every 20 mins after Xfinity did some overnight maintenance.

Suzib6sw

Regular Contributor
Till yesterday , my RT-AX86U Pro (with two RT-AX58u aimesh nodes) all running the latest Merlin firmware, was rock solid. However after Xfinity did some overnight maintenance, the WAN drops every 20 mins almost to the second and is shown in the System log. There is nothing else (set to info or debug) to indicate other potential reasons for this happening in the log. Connecting directly to the Hitron Coda56 Modem and pinging google, did not show any problem except I could only ping IPV6 addresses and not IPV4.
I re-flashed the router, rebooted, (didnt reset) both the routers and modem, Ran Ping against Google, and observed the losts packets every 20 mins that co-incided with the stem logs. I checked the corrected and uncorrected data in the Coda56 and they seemed ok.
In a last ditch attempt to fix this, I turned off IPV6 on the Router and rebooted and since then, no dropped Wan.. I do use DDNS, but the reset of the setup is pretty vanilla.. About 60 devices inc IOT, Guest Networks and no Smart Connect.
So Im wondering is whatever xfinity did is causing these problems and although I dont NEED IPV6 at this moment, what do i need to do else, to enable IPV6 and resolve this.
What process within the router runs every 20 mins? No scripts installed.
Any thoughts would be appreciated.. and yes.. I did look back though the forum for similar issues but nothing seemed to match my circimstances , or I just missed it.
Cheers..
 
What lease period does your ISP use?
(main page, click the wan button)
 
What lease period does your ISP use?
(main page, click the wan button)
DHCP Query frequency is set to Aggressive , I use Cloudflare for the DNS (DOT)
 
That wasn't the question being asked. What is the lease time being issued by your ISP? Click on the WAN/Internet "globe" button on the Network Map page.
Understood., 1 Day..
 
I guess that's the IPv4 lease which you don't have a problem with, so not much help there.

In a last ditch attempt to fix this, I turned off IPV6 on the Router and rebooted and since then, no dropped Wan.
So this is IPv6 related. Perhaps you didn't have IPv6 configured correctly (after Xfinity's changes) on the router?

What are the messages you're seeing in the router's log, can you post them please. If you see the physical interface going down that suggests it's a modem or ISP issue.
 
I guess that's the IPv4 lease which you don't have a problem with, so not much help there.


So this is IPv6 related. Perhaps you didn't have IPv6 configured correctly (after Xfinity's changes) on the router?

What are the messages you're seeing in the router's log, can you post them please. If you see the physical interface going down that suggests it's a modem or ISP issue.
The start of the issue was around 2:53am
Dec 10 02:52:58 udhcpc_wan: hnd_get_phy_status: Temporarily Router cannot get the PHY() status...
Dec 10 02:52:58 wan: finish adding multi routes
Dec 10 02:52:58 openvpn-routing: Applying all killswitches
Dec 10 02:52:59 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Dec 10 02:52:59 wlceventd: wlceventd_proc_event(685): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Dec 10 02:52:59 wlceventd: wlceventd_proc_event(722): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-25
Dec 10 02:53:00 dhcp6_client: WAN Prefix Size Requested:/64, Received:/64
Dec 10 02:53:00 dhcp6_client: bound address 2001:558:6036:84:5c2a:f5f7:8abd:161e/128, prefix 2601:5cf:4700:34ed::/64
Dec 10 02:53:00 rc_service: dhcp6c 28112:notify_rc restart_upnp
Dec 10 02:53:00 rc_service: dhcp6c 28112:notify_rc stop_dnsmasq
Dec 10 02:53:00 rc_service: waitting "restart_upnp"(last_rc:restart_upnp) via dhcp6c ...
Dec 10 02:53:01 rc_service: watchdog 2824:notify_rc start_dnsmasq 0
Dec 10 02:53:02 rc_service: dhcp6c 28112:notify_rc start_dnsmasq 255
Dec 10 02:53:02 rc_service: watchdog 2824:notify_rc start_dnsmasq 1
Dec 10 02:53:02 rc_service: waitting "start_dnsmasq 255"(last_rc:start_dnsmasq 255) via dhcp6c ...
Dec 10 02:53:03 WAN_Connection: WAN was restored.
Dec 10 02:53:04 rc_service: dhcp6c 28112:notify_rc restart_samba
Dec 10 02:53:04 Samba_Server: smb daemon is stopped
Dec 10 02:53:04 rc_service: watchdog 2824:notify_rc start_dnsmasq 2
Dec 10 02:53:04 rc_service: waitting "restart_samba"(last_rc:restart_samba) via dhcp6c ...
Dec 10 02:53:08 rc_service: udhcpc_wan 27584:notify_rc start_dnsmasq 255
Dec 10 02:53:10 WireGuard: Stopping server.
Dec 10 02:53:10 rc_service: udhcpc_wan 27584:notify_rc stop_samba
Dec 10 02:53:10 Samba_Server: smb daemon is stopped
Dec 10 02:53:11 rc_service: udhcpc_wan 27584:notify_rc start_samba
Dec 10 02:53:11 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 00:F3:61:02:40:55, status: 0, reason: Unspecified reason (1), rssi:0
Dec 10 02:53:11 wlceventd: wlceventd_proc_event(685): eth6: Auth 00:F3:61:02:40:55, status: Successful (0), rssi:0
Dec 10 02:53:11 wlceventd: wlceventd_proc_event(722): eth6: Assoc 00:F3:61:02:40:55, status: Successful (0), rssi:-39
Dec 10 02:53:12 WireGuard: Starting server.

From then on this was more or less every 20 mins..
Dec 10 03:33:39 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Dec 10 03:33:39 wlceventd: wlceventd_proc_event(685): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Dec 10 03:33:39 wlceventd: wlceventd_proc_event(722): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-25
Dec 10 03:33:44 WAN_Connection: WAN was restored.
Dec 10 03:33:47 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 0C:DC:91:28:DD:EA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 10 03:33:47 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 0C:DC:91:28:DD:EA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 10 03:33:53 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Dec 10 03:33:53 wlceventd: wlceventd_proc_event(685): eth6: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Dec 10 03:33:53 wlceventd: wlceventd_proc_event(722): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-25

The 2.5Gb LED turns red, the internet Status on the Network map says Disconnected. and then comes back up..

And thanks to all looking at this. I appreciate it.
 
The 2.5Gb LED turns red, the internet Status on the Network map says Disconnected. and then comes back up

Do you have WAN set to 2.5?
Even though you are not using dual WAN it helps to lock it to whatever port you are using for WAN.

Screenshot 2025-12-11 133841.jpg


Side note: Xfinity uses IPv6 only for modem provisioning.

Screenshot 2025-12-11 135256.jpg
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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