NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware 5.1.1.8 issues
Ever since the new firmware update, I have been having issues staying connected. I thought it was my ISP but eventually ended up figuring out it was due to the firmware update. Whenever I have connectivity issues, I roll back to the prior firmware and I am able to connect again. I also tested it out with the previous router I have (different brand). When the issues happened, I used the previous router and my internet worked, but when I reconnected this one it stopped working.
Is it possible to make the router stop updating to the new firmware? I am on Xfinity.
5 Replies
What is having issues saying connected? The CAX80 or a device connected to the CAX80?
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-routerHas a factory reset and setup from scratch been performed since last FW update?
All devices cannot get internet access through the router. The download blinks white and it starts back going though the whole light sequence again starting with the first light. I tried replying twice with the logs but I guess the msgs were too long so it was removed.
Factory reset was initiated every time the issue happened until I realized it was the firmware that was causing the issue. The date this started happening also aligns when the new firmware was released.
This is the event log of when it stops working.
Event Log
Time Priority Description
Fri Nov 22 07:05:50 2024 Notice TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:40 2024 Notice Honoring MDD; IP provisioning mode = IPv6
Fri Nov 22 07:05:27 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:09 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:08 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:00:25 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:18 2024 Notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:17 2024 Notice TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:09 2024 Notice Honoring MDD; IP provisioning mode = IPv6
Fri Nov 22 06:47:57 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:46 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:45 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:41 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:40 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:46:13 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:50 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:21 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:20 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:51 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:49 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:32 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:19 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:06 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:53 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:53 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:50 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:49 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:45 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:45 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;Please post a copy and paste of the modems connection status page.
