AC87U Internet disconnect

[ColinTaylor]

No, nothing within 20 minutes from that event

And it just happened again

Mar 7 07:12:38 dnsmasq-dhcp[7350]: DHCPOFFER(br0) 192.168.1.128 b0:4e:26:19:59:53
Mar 7 07:12:38 dnsmasq-dhcp[7350]: DHCPREQUEST(br0) 192.168.1.128 b0:4e:26:19:59:53
Mar 7 07:12:38 dnsmasq-dhcp[7350]: DHCPACK(br0) 192.168.1.128 b0:4e:26:19:59:53 TPlink-Outlet3
Mar 7 07:36:04 dnsmasq[7350]: Maximum number of concurrent DNS queries reached (max: 150)
Mar 7 07:36:10 dnsmasq[7350]: Maximum number of concurrent DNS queries reached (max: 150)

Did you still have the ping running at this time?

Exactly what happens to me. But like I said, I believe it's incorrect because my IPTV continues working when WAN is listed as disconnected.

I suspect your problem is different. When it happens again, if you upload a copy of your syslog we can look at it.

 

[lifeisfun]

Did you still have the ping running at this time?


....

Yes I did and it skipped about 3 times

 

[ColinTaylor]

Yes I did and it skipped about 3 times

So for how many seconds do you think you lost internet access?

 

[lifeisfun]

So for how many seconds do you think you lost internet access?

About 15s but it varies every time

 

[ColinTaylor]

About 15s but it varies every time

At the moment my money would be on something other than the router being the problem. If it were simply your cable modem rebooting (I'm assuming you have a cable connection) I'd expect to see "WAN" messages in the syslog.

So my current guess would be that it's an upstream issue with your ISP, or possibly a sync problem with your cable modem. Can you log into the modem and check its logs?

 

[lifeisfun]

At the moment my money would be on something other than the router being the problem. If it were simply your cable modem rebooting (I'm assuming you have a cable connection) I'd expect to see "WAN" messages in the syslog.

So my current guess would be that it's an upstream issue with your ISP, or possibly a sync problem with your cable modem. Can you log into the modem and check its logs?

Yes, cable connection, my modem is CGN3 and because is bridged I thought I should be able to access it on 192.168.100.1 but I can't for some strange reason
I remember that I was able to do that with the previous modem. They sent me replacement after I complained about this issue but it did not solve the problem.

Here is the log I sent them at that time from the old modem

1 02/15/19 09:59:14 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
2 02/15/19 09:58:56 90000000 warning MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
3 02/15/19 09:58:35 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
4 02/15/19 09:58:15 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
5 02/15/19 09:58:15 82000300 critical Ranging Request Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
6 02/15/19 09:58:14 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
7 02/15/19 09:58:14 82000300 critical Ranging Request Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
8 02/15/19 09:58:14 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
9 02/15/19 09:58:12 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
10 02/15/19 09:58:12 82000300 critical Ranging Request Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
11 02/15/19 09:58:12 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
12 02/15/19 09:37:09 90000000 warning MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
13 02/15/19 09:36:57 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
14 02/15/19 09:36:39 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
15 02/15/19 09:36:39 82000300 critical Ranging Request Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
16 02/15/19 09:36:39 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
17 02/15/19 09:36:38 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
18 02/15/19 09:36:38 82000300 critical Ranging Request Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
19 02/15/19 09:36:38 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;
20 02/15/19 09:36:38 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=64:77:7d:91:46:ec;CMTS-MAC=00:17:10:93:b0:a7;CM-QOS=1.1;CM-VER=3.0;

 

[ColinTaylor]

Here is the log I sent them at that time from the old modem

Yes that doesn't look good. It only covers two events (at 09:36 and 09:58), so if that was all you were seeing in a week maybe, you could ignore it. If it were happening all the time then there's a bigger problem.

From my very limited experience those don't look like sync issues, but a problem with the upstream ISP equipment.

 

[Thorton]

Are you sure your IPTV is not buffering and that's why the disconnection is not seen on that device?

It's possible. Will need to test it further...

 

[lifeisfun]

Yes that doesn't look good. It only covers two events (at 09:36 and 09:58), so if that was all you were seeing in a week maybe, you could ignore it. If it were happening all the time then there's a bigger problem.

From my very limited experience those don't look like sync issues, but a problem with the upstream ISP equipment.

Thank you very much for your time!
I'll get back to my provider that my problem is still there, also why I can't no longer see my modem stats

 

[lifeisfun]

Just to update....
technician stopped by and redid all the cable connectors, problem gone !
Thanks for the help!