NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Sporadic router freeze on CAX80 - only when using WiFi
My Problem: Sporadic router freeze on CAX80 - only when using WiFi
Am looking for help troubleshooting assistance. CAX80, hardware Version: 1.01, Firmware Version: v1.02.08. Connected to Xfinity cable. Speed tests consistently 350-400 Mbps download, 10-11Mbps upload.
When directly connected via internet cable, I have no problems whatsoever. When connected to WiFi on any device (iPad, SmartTV, etc using either 5 or 2.4 GHz) occasionally the router freezes up for a minute or two (and sometimes longer). Sometimes once in two or three weeks and sometimes a few times per day or week. I don't believe that my internet service provider is the problem since I can use my neighbor's Wi-Fi and don't see these problems even when my router is frozen (same Xfinity service provider and plan, in an apartment building, so believe it is a similar service and have had Xfinity come onsite and rule out any connectivity issues).
Log files show a constant stream of various DoS attacks. They are endless so I can't figure out if the router freezes are due to DoS attacks or something else but from reading various sites, some suggest that the router writing log files for so many DOS events could cause some performance failures or dropped events. Some say that the way around these freezes is to limit the logging of DoS attacks, but I cannot figure out how to do that on my router model CAX80.
Does anyone have advice?
Here is an example of some of the DoS logs, they are constantly being logged each day with no pattern I can see:
| [DoS attack] ACK scan SPT:443 DPT:59079 | 5 | Thu Jan 4 11:16:52 2024 | 24.62.94.49:59079 | 151.101.193.140:443 |
| [DoS attack] ACK scan SPT:443 DPT:58876 | 1 | Thu Jan 4 10:58:32 2024 | 24.62.94.49:58876 | 34.111.8.32:443 |
| [DoS attack] ACK scan SPT:443 DPT:58875 | 2 | Thu Jan 4 10:58:32 2024 | 24.62.94.49:58875 | 34.111.8.32:443 |
| [DoS attack] ACK scan SPT:443 DPT:58876 | 1 | Thu Jan 4 10:58:31 2024 | 24.62.94.49:58876 | 34.111.8.32:443 |
7 Replies
Your behind on FW:
What wifi channels are you using?
What wifi devices do you all have connected?
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-routerThanks for the reply! Let me know if there is something I left out. My info below:
Firmware
I realized I put in the cable firmware and not the router firmware. I didn't realize that there were separate firmware setups for cable and router, I am current on router updates, here they are for reference:
Firmware Version V2.1.5.2 Cable Firmware Version V1.02.08 What wifi channels are you using?
For 2.4 GHz, channel is set to auto and currently 9. 5GHz is set to 48. I've tried switching them around with no change in behavior.
What wifi devices do you all have connected?
iPhone, 2 iPads, Macbook, LG SmartTV.
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-m...Cable ConnectionCancel ApplyCable Diagnostic Status: Good Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info. Internet Access: Downstream Status: Upstream Status: Refresh Save Cable Diagnostic Info Advanced Information Frequency Start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency Time Priority Description Fri Jan 5 14:39:14 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 14:37:24 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 14:35:30 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 14:29:50 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 13:40:00 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 13:36:27 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 11:10:07 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 11:06:24 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 09:54:29 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 09:52:48 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 07:48:06 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Jan 5 07:43:40 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 22:30:11 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 22:28:37 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 21:55:55 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 21:49:14 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 20:41:29 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 20:35:06 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 20:33:21 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 20:29:57 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 18:07:37 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 18:05:43 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 16:09:40 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 16:05:16 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 15:48:34 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 15:42:08 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 15:13:35 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 15:13:02 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 12:23:59 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 12:23:57 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 12:23:31 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 1 00:00:50 1970 Notice (6) Honoring MDD; IP provisioning mode = IPv6 Thu Jan 1 00:00:44 1970 Critical (3) UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 1 00:00:44 1970 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 4 12:13:34 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 1 00:00:46 1970 Critical (3) UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jan 1 00:00:44 1970 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Tue Jan 2 20:23:51 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Wed Dec 20 23:11:58 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1; Sat Dec 16 10:13:54 2023 Critical (3) UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
There is more data for the cable connections status page that if you can capture and post please.
Sorry about that, didn't cut and paste properly! Here is the additional cable info:
Cable ConnectionCancel ApplyCable Diagnostic Status: Good Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info. Internet Access: Downstream Status: Upstream Status: Refresh Save Cable Diagnostic Info Advanced Information Frequency Start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency Startup Procedure Procedure Status Comment Acquire Downstream Channel 565 MHz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked 256 QAM 20 565750000 Hz 2.2 dBmV 45.3 dB 27 110 2 Locked 256 QAM 13 523750000 Hz 1.5 dBmV 45.4 dB 30 104 3 Locked 256 QAM 14 529750000 Hz 2.2 dBmV 46.0 dB 50 79 4 Locked 256 QAM 15 535750000 Hz 2.5 dBmV 46.2 dB 46 97 5 Locked 256 QAM 16 541750000 Hz 2.4 dBmV 46.2 dB 29 105 6 Locked 256 QAM 17 547750000 Hz 1.7 dBmV 45.5 dB 27 105 7 Locked 256 QAM 18 553750000 Hz 2.2 dBmV 45.0 dB 28 110 8 Locked 256 QAM 19 559750000 Hz 2.9 dBmV 44.5 dB 27 106 9 Locked 256 QAM 21 571750000 Hz 1.9 dBmV 45.6 dB 37 95 10 Locked 256 QAM 22 577750000 Hz 2.5 dBmV 45.1 dB 53 82 11 Locked 256 QAM 23 583750000 Hz 2.9 dBmV 45.3 dB 38 99 12 Locked 256 QAM 24 589750000 Hz 3.1 dBmV 45.2 dB 30 110 13 Locked 256 QAM 25 595750000 Hz 2.6 dBmV 33.7 dB 52 116 14 Locked 256 QAM 26 601750000 Hz 3.5 dBmV 36.0 dB 66 126 15 Locked 256 QAM 27 607750000 Hz 3.2 dBmV 44.9 dB 27 104 16 Locked 256 QAM 28 613750000 Hz 2.6 dBmV 45.8 dB 24 110 17 Locked 256 QAM 29 619750000 Hz 3.0 dBmV 45.7 dB 34 104 18 Locked 256 QAM 30 625750000 Hz 3.1 dBmV 43.8 dB 712 114 19 Locked 256 QAM 31 631750000 Hz 3.1 dBmV 42.7 dB 3858 112 20 Locked 256 QAM 32 637750000 Hz 3.1 dBmV 40.8 dB 36733 1073 21 Locked 256 QAM 33 643750000 Hz 3.7 dBmV 44.5 dB 31 105 22 Locked 256 QAM 34 649750000 Hz 4.4 dBmV 46.4 dB 23 112 23 Locked 256 QAM 35 655750000 Hz 4.5 dBmV 46.5 dB 21 116 24 Locked 256 QAM 36 661750000 Hz 4.3 dBmV 46.4 dB 43 94 25 Locked 256 QAM 37 667750000 Hz 4.3 dBmV 46.3 dB 33 100 26 Locked 256 QAM 38 673750000 Hz 4.8 dBmV 45.5 dB 27 108 27 Locked 256 QAM 39 679750000 Hz 4.8 dBmV 46.6 dB 26 104 28 Locked 256 QAM 40 685750000 Hz 4.6 dBmV 46.5 dB 32 99 29 Locked 256 QAM 41 691750000 Hz 4.7 dBmV 46.5 dB 35 103 30 Locked 256 QAM 42 697750000 Hz 5.4 dBmV 46.8 dB 32 103 31 Locked 256 QAM 43 703750000 Hz 5.5 dBmV 46.8 dB 37 97 32 Locked 256 QAM 44 709750000 Hz 5.0 dBmV 46.6 dB 28 103 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 39.3 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 39.5 dBmV 3 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 38.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 39.5 dBmV 5 Not Locked Unknown 0 0 0 0.0 dBmV 6 Not Locked Unknown 0 0 0 0.0 dBmV 7 Not Locked Unknown 0 0 0 0.0 dBmV 8 Not Locked Unknown 0 0 0 0.0 dBmV Downstream OFDM Channels Channel Lock
StatusModulation /
Profile IDChannel
IDFrequency Power SNR /
MERActive Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 193 957000000 Hz -0.32 dBmV 42.0 dB 148 ~ 3947 755888644 506855611 91 2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV Extended Upstream Transmit Power Enable Extended Upstream Transmit Power Current System Time:Sat Jan 06 11:39:57 2024 System Up Time:1 days 23:17:23 Power levels are ok and with in specs.
We see correctables and uncorrectables that should be mostly zeros.
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.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
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
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.htmlTry changing channels to 1,6 or 11 on 2.4Ghz and 40, 44 or 48 on 5Ghz.
Has a factory reset and setup from scratch been performed since last update?
