NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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. ...
A lot of us have reached out to Comcast/Xfinity, multiple have even stated they had techs come out and test the line. I've chatted with Xfinity and initially they told me everything was good on their end. I posted on the Xfinity forums and, it took a couple days, but they reached back out and are investigating. MY guess is that this is NOT an ISP issue as SEVERAL of us have downgraded to .5 and the issue went away, only to return again when NG forces an update to .7
As for Support from NG, I did submit a ticket along with finding and posting to this Forum. They said that I need to call in for Support because I an Extended warranty (ALWAYS buy the any extended warranty for this very reason). I haven't given them a call yet, I don't really see a need to since we know it's an FW issue that is resolved by downgrading.
Isn't funny though how they are saying to downgrade to .5? What about .6? OH YEAH, .6 had IT'S own problems too. The quicker NG pulls their heads out the quicker this can be resolved.
Xfinity has confirmed that the IP Address showing as the Source for the DoS Land Attack IS my assigned IP Address from them.
SO NG needs to answer
1) WHY they removed the Enable/Disable Update Feature
2) Need to explain HOW the FW update is forcing the Router to reboot daily, some of us MULTIPLE times a day
3) Need to explain WHY DoS land attacks are generating from the assigned IP Address from our ISP under FW V2.1.3.7
4) AND when can we expect a fix.
Otherwise, we can go the longer, more costly route for filing complains with the Consumer Protection Agency, BBB, etc. or those who have already stated filing a Class Action. Come on NG, do the right thing here.
- Noting that manually flashing the 2.1.3.7 firmware (on top of the OTA 2.1.3.7) did not help.