386.7 Internet Dropping every few days/weeks

[jkexbx]

I'm using a RT-AX86U running 386.7. Every so often the internet will go down. I was able to catch it occurring last night and have that portion of the logs below.

Can anyone shed some light on what might be going on?

Jul  6 00:18:29 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jul  6 00:18:29 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jul  6 00:18:29 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe832 (36/160)
Jul  6 00:18:29 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jul  6 00:18:29 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jul  6 00:18:29 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe932 (40/160)
Jul  6 00:18:29 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jul  6 00:18:29 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jul  6 00:18:29 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xea32 (44/160)
Jul  6 00:18:29 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jul  6 00:18:29 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jul  6 00:18:29 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xeb32 (48/160)
Jul  6 00:19:01 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
Jul  6 00:19:01 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: 1e) Link DOWN.
Jul  6 00:19:07 WAN_Connection: WAN(0) link down.
Jul  6 00:19:42 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2, 3 --> 5 ] [ 7 --> 8 ]
Jul  6 00:19:42 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: 1e) Link Up at 2500 mbps full duplex
Jul  6 00:19:42 WAN_Connection: WAN(0) link up.
Jul  6 00:19:42 rc_service: wanduck 1432:notify_rc restart_wan_if 0
Jul  6 00:19:42 wsdd2[25146]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  6 00:19:45 wsdd2[25146]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  6 00:19:46 wan: finish adding multi routes
Jul  6 00:19:46 rc_service: udhcpc_wan 4223:notify_rc stop_samba
Jul  6 00:19:46 rc_service: udhcpc_wan 4223:notify_rc start_samba
Jul  6 00:19:46 rc_service: waitting "stop_samba" via udhcpc_wan ...
Jul  6 00:19:46 wsdd2[25146]: Terminated received.
Jul  6 00:19:47 Samba_Server: smb daemon is stopped
Jul  6 00:19:47 WAN_Connection: WAN was restored.
Jul  6 00:19:48 dhcp_client: bound 192.168.100.10/255.255.255.0 via 192.168.100.1 for 30 seconds.
Jul  6 00:19:48 Samba_Server: daemon is started
Jul  6 00:20:15 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 40:74:E0:CD:51:9A, status: 0, reason: Unspecified reason (1)
Jul  6 00:20:16 wlceventd: wlceventd_proc_event(505): eth7: Auth 40:74:E0:CD:51:9A, status: Successful (0)
Jul  6 00:20:16 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 40:74:E0:CD:51:9A, status: Successful (0)
Jul  6 00:20:19 wlceventd: wlceventd_proc_event(486): eth7: Disassoc EC:5C:68:78:CE:A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:19 wlceventd: wlceventd_proc_event(486): eth7: Disassoc EC:5C:68:78:CE:A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:22 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 92:C8:AE:92:DD:2A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:22 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 92:C8:AE:92:DD:2A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:22 wlceventd: wlceventd_proc_event(505): eth7: Auth 92:C8:AE:92:DD:2A, status: Successful (0)
Jul  6 00:20:22 wlceventd: wlceventd_proc_event(534): eth7: Assoc 92:C8:AE:92:DD:2A, status: Successful (0)
Jul  6 00:20:27 wlceventd: wlceventd_proc_event(505): eth7: Auth EC:5C:68:78:CE:A3, status: Successful (0)
Jul  6 00:20:27 wlceventd: wlceventd_proc_event(534): eth7: Assoc EC:5C:68:78:CE:A3, status: Successful (0)
Jul  6 00:20:32 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 40:74:E0:CD:51:9A, status: 0, reason: Unspecified reason (1)
Jul  6 00:20:43 wsdd2[4430]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  6 00:20:43 wlceventd: wlceventd_proc_event(486): eth7: Disassoc EC:5C:68:78:CE:A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:43 wlceventd: wlceventd_proc_event(486): eth7: Disassoc EC:5C:68:78:CE:A3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  6 00:20:43 wsdd2[4430]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  6 00:20:43 wlceventd: wlceventd_proc_event(505): eth7: Auth EC:5C:68:78:CE:A3, status: Successful (0)
Jul  6 00:20:43 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc EC:5C:68:78:CE:A3, status: Successful (0)
Jul  6 00:20:43 wan: finish adding multi routes
Jul  6 00:20:43 rc_service: udhcpc_wan 5205:notify_rc stop_samba
Jul  6 00:20:43 rc_service: udhcpc_wan 5205:notify_rc start_samba
Jul  6 00:20:43 rc_service: waitting "stop_samba" via udhcpc_wan ...
Jul  6 00:20:43 wsdd2[4430]: Terminated received.
Jul  6 00:20:43 Samba_Server: smb daemon is stopped
Jul  6 00:20:44 dhcp_client: bound 69.255.6.222/255.255.248.0 via 69.255.0.1 for 271268 seconds.
Jul  6 00:20:44 Samba_Server: daemon is started
Jul  6 00:20:45 wlceventd: wlceventd_proc_event(505): eth7: Auth 40:74:E0:CD:51:9A, status: Successful (0)
Jul  6 00:20:45 wlceventd: wlceventd_proc_event(534): eth7: Assoc 40:74:E0:CD:51:9A, status: Successful (0)

 

[dave14305]

I would guess your modem rebooted. When the WAN came back up, it had a 192.168.100.10 address until the modem synced with the ISP network. Check your modem logs.

 

[Tech9]

I would guess your modem rebooted.

This modem must be really fast - 40 seconds.

 

[dave14305]

This modem must be really fast - 40 seconds.

Reminds me of something my wife said to me once...or twice...

 

[Tech9]

Reminds me of something

This one got back in action in 40 seconds. What you are talking about is perhaps keeping the connection for 40 seconds...

 

[eibgrad]

I have no idea what to make of a WAN connection that drops out around midnight, but reestablishes itself a mere 35 seconds later. I doubt I would ever notice it if happened to me. Could just be the ISP resetting their network for some reason. But there's no indication there's anything wrong w/ the router.

Now if this happens every 20 mins, even every couple hours, that would be different. But every few days, perhaps weeks, you have a momentary glitch? Could be your ISP just isn't quite as reliable as others, at least if the standard is 100% perfect continuous connectivity. But I don't know if that's a reasonable expectation from any ISP. Heck, my ISP (Cox) drops out *completely* at least twice every year for some unknown reason, and can last for several hours, perhaps overnight! I've just come to anticipate it because I don't expect 100% reliability from any of them.

Understand, I'm NOT completely dismissing the possibility of an issue here, but based on what the OP has reported SO FAR, I see nothing that couldn't be explained as SOP for the average ISP.

 

[RMerlin]

Jul 6 00:19:01 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: 1e) Link DOWN.

Ethernet link going down then up does not necessarily indicate that the modem has completed its reboot. Only that the Ethernet port is once again powered on. For a typical DOCSIS model, 40 seconds looks about right to me. After that the rest of the modem still needs to re-establish the RF connection (if dealing with cable), obtain a DHCP lease, etc...

So yeah, first thing I'd suspect is the modem itself (and the Internet connection, as some modems will reboot when they lose the signal from the ISP).

 

[Tech9]

Ethernet link going down then up does not necessarily indicate that the modem has completed its reboot.

This one indicates WAN restored in 40 seconds. The router got DNS query resolution, no?

Jul 6 00:19:07 WAN_Connection: WAN(0) link down.
Jul 6 00:19:47 WAN_Connection: WAN was restored.

My TekSavvy Rogers Hitron modem needs like 3 minutes to complete a reboot cycle with sync.

 

[dave14305]

This one indicates WAN restored in 40 seconds. The router got DNS query resolution, no?

Jul 6 00:19:07 WAN_Connection: WAN(0) link down.
Jul 6 00:19:47 WAN_Connection: WAN was restored.

My TekSavvy Rogers Hitron modem needs like 3 minutes to complete a reboot cycle with sync.

There was no valid public IP until 00:20:44.

 

[Tech9]

There was no valid public IP until 00:20:44.

Is this the ugly wanduck guy? WAN was restored... but not really. I would expect WAN status is tied to Network Detection, DNS/ping. This is what it is for - to detect the WAN status. The syslog is incorrect.

 

[dave14305]

Is this the ugly wanduck guy? WAN was restored... but not really. I would expect WAN status is tied to Network Detection, DNS/ping. This is what it is for - to detect the WAN status. The syslog is incorrect.

Judge for yourself. Can you unravel their logic?

https://github.com/RMerl/asuswrt-merlin.ng/blob/d1340bd88e3163a0b8151c14e6592cc21ca0f1e7/release/src/router/rc/wanduck.c#L3053

 

[iamjayder]

I have this issue too. When I upgraded to 386.7 my wireless suddenly disconnects like twice or thrice a day. I even did a reset and then re-uploading the firmware again but the issue still persists. I connected to my ISPs modem just to check if the issue was coming from there but it wasn't. That's why I went back to 386.5_2 and I am not getting this issue. I also noticed that this issue is also present in the stock firmware 3.0.0.4.386.48631 and that's why I never upgraded to this version from Asus.

 

[jkexbx]

I have this issue too. When I upgraded to 386.7 my wireless suddenly disconnects like twice or thrice a day. I even did a reset and then re-uploading the firmware again but the issue still persists. I connected to my ISPs modem just to check if the issue was coming from there but it wasn't. That's why I went back to 386.5_2 and I am not getting this issue. I also noticed that this issue is also present in the stock firmware 3.0.0.4.386.48631 and that's why I never upgraded to this version from Asus.

Were you able to check logs and see the same series of WAN dropping and connecting?

 

[jkexbx]

This one indicates WAN restored in 40 seconds. The router got DNS query resolution, no?

Jul 6 00:19:07 WAN_Connection: WAN(0) link down.
Jul 6 00:19:47 WAN_Connection: WAN was restored.

My TekSavvy Rogers Hitron modem needs like 3 minutes to complete a reboot cycle with sync.

I'm running a Motorola mb8611. The logs are pretty poor. The only thing showing up was, but there isn't any timestamps so it could be completely unrelated.

Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:77:a3:57;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1

 

[Tech9]

If it's only once - ignore it. If you have a full page of such records - call your ISP to fix.

 

[jkexbx]

If it's only once - ignore it. If you have a full page of such records - call your ISP to fix.

It's a full page, I'll call them then

 

[username0475]

It's a full page, I'll call them then

Did you ever get this resolved?

Which ISP did you work with?

A bunch of us are having issues with the MB8611 Modem on Xfinity starting in December & more so frequently now (~1x per 30 mins in some instances).
But no one on either side is owning up to the issue even after the modem has been rock solid for so many.

Want to hear if you had some news on your issue which sounds exactly (logs & all) like current problems we are having.

 

[Viktor Jaep]

Did you ever get this resolved?

Which ISP did you work with?

A bunch of us are having issues with the MB8611 Modem on Xfinity starting in December & more so frequently now (~1x per 30 mins in some instances).
But no one on either side is owning up to the issue even after the modem has been rock solid for so many.

Want to hear if you had some news on your issue which sounds exactly (logs & all) like current problems we are having.

Oh great... not what I wanted to hear. I just ordered (and was delivered today) a Motorola MB8611 modem today to take advantage of my 1.5Gb bandwidth and 2.5Gb port on the GT-AX6000. I was planning on activating it tomorrow morning, so I'll check in if I experience any weirdness.

Have you been able to log into the modem interface and look at its logs? That's what I had to do a few years ago when troubleshooting an Xfinity connection issue.

 

[Tech9]

Did you ever get this resolved?

I don't think so. User @jkexbx was last seen on Jul 8, 2022. Perhaps they are still trying to connect.

 

[Viktor Jaep]

Did you ever get this resolved?

Which ISP did you work with?

A bunch of us are having issues with the MB8611 Modem on Xfinity starting in December & more so frequently now (~1x per 30 mins in some instances).
But no one on either side is owning up to the issue even after the modem has been rock solid for so many.

Want to hear if you had some news on your issue which sounds exactly (logs & all) like current problems we are having.

Hey @username0475 ... I decided to install my MB8611 yesterday evening... so I've been going about 22hrs with no ill effects or any WAN issues to report as of yet. I'm so glad to see the process is so easy now for us consumers to add our own equipment to the mix. Just a few years back, you still had to deal with techs and house visits to make this all happen.

Running speedtest through RTRMON is yielding me about 1440Mbps, so things seem to be working well...

As I mentioned, I had some trouble with Xfinity a few years back, and they kept blaming it on my own equipment, or the wiring in our house... I was able to use the logs I gathered from the modem itself to show that there was some serious connectivity issues, voltage, latency, etc. happening. I asked if there was anything else they could do from a troubleshooting aspect, and Xfinity support ended up putting some kind of a monitor on my line to watch the stats more closely, and ended up determining from that that the issue was upstream. Fixed next day, and have had a strong uninterrupted signal ever since.