NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Moreno279
Jun 11, 2022Aspirant
CAX80 keeps rebooting
For the past 3 days my CAX80 has been rebooting every 4 to 5 hours. I’ve tried connecting the power source directly to an outlet and that didn’t work. I did a factory reset and that also didn’t work. ...
Omnitron
Jun 15, 2022Guide
The issue is that firmware upgrades get pushed by the ISP themselves repeatedly (once they ‘promote’ it), such as Xfinity. Reverting to 2.1.3.5 only lasted until the following night for us, then by morning it was back on 2.1.3.7.
The issue might be that 2.1.3.7 is just bad firmware, but it could also be that one of the setting defaults changed since 2.1.3.5. For example, I noticed that “Starting Frequency” under Cable Connection has changed from 405MHz to 507MHz, so next time we get a disconnect, I’ll try forcing the old value to see if it helps. If it doesn’t, we might have no choice but to wait for another firmware fix by Netgear.
The issue might be that 2.1.3.7 is just bad firmware, but it could also be that one of the setting defaults changed since 2.1.3.5. For example, I noticed that “Starting Frequency” under Cable Connection has changed from 405MHz to 507MHz, so next time we get a disconnect, I’ll try forcing the old value to see if it helps. If it doesn’t, we might have no choice but to wait for another firmware fix by Netgear.
tamanaco
Jun 15, 2022Apprentice
"The issue is that firmware upgrades get pushed by the ISP themselves repeatedly (once they ‘promote’ it), such as Xfinity. Reverting to 2.1.3.5 only lasted until the following night for us, then by morning it was back on 2.1.3.7."
Omnitron- Someone correct me if I'm wrong, but my understanding is that the ISPs can push updates to the "Modem" side of the router. The router side is updated by Netgear either via OTA push/pull or manually via locally downloaded firmware. You can download the v2.1.3.7 firmware directly from Netgear and update your router yourself, but you can't get the firmware for the Modem side (It's ISP dependent).
- OmnitronJun 15, 2022GuideWould be interesting to get official confirmation that the ISP cannot possibly be the one pushing 2.1.3.7, and that it’s Netgear OTA pushing it instead (I didn’t know OTA pushes were a thing).
Either way, would be good to collectively confirm if the change in Cable Connection -> Starting Frequency is the culprit or not, since that’s the only user adjustable field that seems to have changed since 2.1.3.5.- FURRYe38Jun 15, 2022Guru - Experienced User
Has anyone tried applying v.7 FW manually, after it's applied, factory reset and then setup from scratch.
I've NOT seen any odd reboots on my CAX80 with v.7 loaded.
One main issue that would cause a reboot is that the ISP signal has stopped or signal on the line is degraded. Remember the CAX80 will auto reboot if ANY signal on the line becomes bad or the signal completely stops for any reason.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router?article=24311
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/- milad6387Jun 15, 2022Guide
"One main issue that would cause a reboot is that the ISP signal has stopped or signal on the line is degraded. Remember the CAX80 will auto reboot if ANY signal on the line becomes bad or the signal completely stops for any reason."
But if it is a ISP signal issue, then we should be seeing it when we go to .5, however, it appears that most people (including myself, so far) have not experienced these issues on .5. So I just don't see how that could be a ISP signal issue.