Orbi WiFi 7 RBE973
Reply

CAX30 Poor Cable Connection Status

IcedTea
Aspirant

CAX30 Poor Cable Connection Status

Hi, I have Xfinitys Gig internet speed plan and recently purchased a CAX30S. The cable connection is poor and I've tried swapping out coax cables. According to the downstream status, it says Downstream SNR and power levels are poor "Downstream power is poor (-9.9 dBmV). The recommended level is between -10dBmV to 10dBmV." I'm not sure if there's anything I can do before I contact my ISP.

Below are the diagnostic results:

Startup Procedure

ProcedureStatusComment
Acquire Downstream Channel531000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDIPv6 only
 
Downstream Bonded Channels
 
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectabables
1Locked256 QAM20531000000 Hz-8.5 dBmV32.5 dB00
2Locked256 QAM13489000000 Hz-8.6 dBmV41.3 dB00
3Locked256 QAM14495000000 Hz-8.8 dBmV42.3 dB00
4Locked256 QAM15501000000 Hz-8.7 dBmV42.4 dB00
5Locked256 QAM16507000000 Hz-8.6 dBmV42.4 dB00
6Locked256 QAM17513000000 Hz-8.5 dBmV42.4 dB00
7Locked256 QAM18519000000 Hz-8.9 dBmV41.6 dB00
8Locked256 QAM19525000000 Hz-8.8 dBmV38.0 dB00
9Locked256 QAM21537000000 Hz-8.5 dBmV38.3 dB00
10Locked256 QAM22543000000 Hz-8.9 dBmV41.9 dB00
11Locked256 QAM23549000000 Hz-9.2 dBmV41.8 dB00
12Locked256 QAM24555000000 Hz-8.9 dBmV40.7 dB00
13Locked256 QAM25561000000 Hz-8.6 dBmV41.4 dB00
14Locked256 QAM26567000000 Hz-8.7 dBmV40.9 dB00
15Locked256 QAM27573000000 Hz-9.3 dBmV35.9 dB00
16Locked256 QAM28579000000 Hz-9.2 dBmV39.6 dB00
17Locked256 QAM29585000000 Hz-8.9 dBmV41.9 dB00
18Locked256 QAM30591000000 Hz-8.8 dBmV41.7 dB00
19Locked256 QAM31597000000 Hz-9.3 dBmV41.4 dB00
20Locked256 QAM32603000000 Hz-9.5 dBmV26.5 dB7328154193792
21Locked256 QAM33609000000 Hz-9.2 dBmV31.8 dB00
22Locked256 QAM34615000000 Hz-8.8 dBmV41.9 dB00
23Locked256 QAM35621000000 Hz-9.0 dBmV41.5 dB00
24Locked256 QAM36627000000 Hz-9.2 dBmV41.5 dB00
25Locked256 QAM37633000000 Hz-9.2 dBmV41.4 dB00
26Locked256 QAM38639000000 Hz-8.8 dBmV41.7 dB00
27Locked256 QAM39645000000 Hz-9.1 dBmV41.7 dB00
28Locked256 QAM40651000000 Hz-9.3 dBmV41.6 dB00
29Locked256 QAM41657000000 Hz-9.8 dBmV41.2 dB00
30Locked256 QAM42663000000 Hz-9.1 dBmV41.7 dB00
31Locked256 QAM43669000000 Hz-9.3 dBmV41.5 dB00
32Locked256 QAM44675000000 Hz-9.2 dBmV41.2 dB00
 
Upstream Bonded Channels
 
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec16400000 Hz43.3 dBmV
2LockedATDMA25120 Ksym/sec22800000 Hz43.8 dBmV
3LockedATDMA35120 Ksym/sec29200000 Hz44.3 dBmV
4LockedATDMA45120 Ksym/sec35600000 Hz44.8 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0 dBmV
 
Downstream OFDM Channels
 
ChannelChannel IDFrequencyPowerSNR/MERActive Subcarrier Number RangeTotal CodewordsUncorrectable Codewords
1193957000000 Hz-12.2 dBmV38.3 dB148 ~ 394715308580
200 Hz0 dBmV0 dB0 ~ 000
 
Upstream OFDMA Channels
 
ChannelUpstreamIsMutedRanging StatusSubcarrier Zero FrequencyActive Subcarrier Number RangeSymbols Per FrameTx Power
1 Other0 MHz0 ~ 000 dBmV
2 Other0 MHz0 ~ 000 dBmV
Message 1 of 9
FURRYe38
Guru

Re: CAX30 Poor Cable Connection Status

Message 2 of 9
IcedTea
Aspirant

Re: CAX30 Poor Cable Connection Status

Here is the log

[admin login] from source 192.168.1.2 Apr 30 15:58:07
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 30 13:54:56
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 30 13:54:44
[admin login] from source 192.168.1.2 Apr 30 13:34:45
[DHCP IP: (192.168.1.6)] to MAC address d2:0c:37:54:86:c4, Apr 30 13:25:43
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Apr 30 13:25:41
[DHCP IP: (192.168.1.10)] to MAC address fe:67:85:ba:43:20, Apr 30 13:24:20
[admin login] from source 192.168.1.2 Apr 30 13:21:47
[Internet connected] IP address: 24.18.228.24, Apr 30 13:21:14
[Initialized, firmware version: V2.2.2.2], Apr 30 13:19:44
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Dec 14 17:49:00
[admin login] from source 192.168.1.2 Apr 30 13:18:42
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Apr 30 11:50:55
[WLAN access rejected: incorrect security] from MAC address 96:05:27:0e:81:a7, Apr 30 10:44:44
[WLAN access rejected: incorrect security] from MAC address 96:05:27:0e:81:a7, Apr 30 10:44:36
[WLAN access rejected: incorrect security] from MAC address 96:05:27:0e:81:a7, Apr 30 10:44:29
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 30 10:30:20
[DHCP IP: (192.168.1.10)] to MAC address fe:67:85:ba:43:20, Apr 30 10:01:20
[DHCP IP: (192.168.1.6)] to MAC address d2:0c:37:54:86:c4, Apr 30 09:07:59
[WLAN access rejected: incorrect security] from MAC address 20:1a:94:21:d1:c2, Apr 30 07:22:49
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 30 06:05:49
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 30 06:02:59
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 30 06:00:20
[DHCP IP: (192.168.1.11)] to MAC address ea:1a:78:f0:e0:19, Apr 29 22:53:25
[DHCP IP: (192.168.1.10)] to MAC address fe:67:85:ba:43:20, Apr 29 22:00:44
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:46:12
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:45:55
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:31:39
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:31:27
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:31:10
[DHCP IP: (192.168.1.9)] to MAC address fe:67:85:ba:43:20, Apr 29 21:16:29
[DHCP IP: (192.168.1.6)] to MAC address d2:0c:37:54:86:c4, Apr 29 21:01:53
[WLAN access rejected: incorrect security] from MAC address ac:00:7a:ac:69:30, Apr 29 19:08:50
[WLAN access rejected: incorrect security] from MAC address ac:00:7a:ac:69:30, Apr 29 19:07:14
[DHCP IP: (192.168.1.5)] to MAC address d2:0c:37:54:86:c4, Apr 29 18:27:58
[admin login] from source 192.168.1.9 Apr 29 18:09:25
[admin login] from source 192.168.1.9 Apr 29 18:09:23
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 29 18:02:04
[DHCP IP: (192.168.1.3)] to MAC address 26:91:5f:ac:de:44, Apr 29 18:01:12
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 29 17:59:12
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Apr 29 17:58:48
[DHCP IP: (192.168.1.6)] to MAC address ea:1a:78:f0:e0:19, Apr 29 17:57:58
[admin login] from source 192.168.1.2 Apr 29 17:57:54
[admin login failure] from source 192.168.1.2 Apr 29 17:57:44
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 29 17:57:23
[DHCP IP: (192.168.1.5)] to MAC address fe:67:85:ba:43:20, Apr 29 17:56:55
[Internet connected] IP address: 24.18.228.24, Apr 29 17:54:18
[Initialized, firmware version: V2.2.2.2], Dec 14 17:49:08
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Dec 14 17:49:00
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 30 00:42:19
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 30 00:42:19
[admin login] from source 192.168.1.2 Apr 29 17:31:32
[DHCP IP: (192.168.1.9)] to MAC address c8:7f:54:6c:99:1d, Apr 29 17:29:44
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 29 17:06:35
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 29 16:54:47
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 23:54:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 23:54:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 23:42:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 23:42:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 23:18:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 23:18:09
[DHCP IP: (192.168.1.6)] to MAC address ea:1a:78:f0:e0:19, Apr 29 16:01:57
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 22:54:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 22:54:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 22:06:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 22:06:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 21:18:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 21:18:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 21:06:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 21:06:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 20:54:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 20:54:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 20:42:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 20:42:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 20:30:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 20:30:08
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 29 13:06:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 20:05:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 20:05:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 19:17:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 19:17:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 19:05:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 19:05:59
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Apr 29 11:47:14
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 18:41:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 18:41:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 18:29:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 18:29:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 17:53:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 17:53:59
[DHCP IP: (192.168.1.3)] to MAC address d2:0c:37:54:86:c4, Apr 29 10:48:04
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 17:41:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 17:41:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 17:29:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 17:29:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 16:41:49
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 16:41:49
[DHCP IP: (192.168.1.5)] to MAC address fe:67:85:ba:43:20, Apr 29 09:01:16
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 15:53:48
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 15:53:48
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 15:41:39
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 15:41:39
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 15:29:39
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 15:29:39
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 15:17:39
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 15:17:39
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 14:41:29
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 14:41:29
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 14:29:29
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 14:29:29
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 14:05:29
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 14:05:29
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 13:41:28
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 13:41:28
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 29 06:23:19
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 13:05:19
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 13:05:19
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 12:53:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 12:53:18
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 12:41:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 12:41:18
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 29 05:02:58
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 11:53:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 11:53:08
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 29 04:41:17
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 11:16:59
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 11:16:59
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 10:52:58
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 10:52:58
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 09:40:48
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 09:40:48
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 09:16:39
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 09:16:39
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 29 02:08:54
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 08:28:38
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 08:28:38
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 08:16:39
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 08:16:39
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 29 00:10:38
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 06:52:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 06:52:18
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 06:40:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 06:40:18
[DHCP IP: (192.168.1.3)] to MAC address d2:0c:37:54:86:c4, Apr 28 23:23:52
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 06:16:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 06:16:18
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 06:04:09
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 06:04:09
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 05:52:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 05:52:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 05:40:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 05:40:08
[DHCP IP: (192.168.1.5)] to MAC address fe:67:85:ba:43:20, Apr 28 22:19:39
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 05:16:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 05:16:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 05:04:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 05:04:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 04:52:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 04:52:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 04:40:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 04:40:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 04:28:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 04:28:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 04:16:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 04:16:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 03:40:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 03:40:08
[DHCP IP: (192.168.1.6)] to MAC address ea:1a:78:f0:e0:19, Apr 28 20:37:31
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 03:04:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 03:04:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 02:52:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 02:52:08
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 28 19:05:52
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 01:40:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 01:40:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 00:52:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 00:52:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 00:40:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 00:40:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 29 00:28:08
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 29 00:28:08
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 22:51:57
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 22:51:57
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 22:15:48
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 22:15:48
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 21:51:47
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 21:51:47
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 21:39:47
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 21:39:47
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 21:27:38
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 21:27:38
[DHCP IP: (192.168.1.2)] to MAC address 00:d8:61:fb:92:c7, Apr 28 14:11:21
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 28 14:09:15
[DHCP IP: (192.168.1.6)] to MAC address ea:1a:78:f0:e0:19, Apr 28 13:47:56
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 20:39:27
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 20:39:27
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 19:51:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 19:51:18
[DHCP IP: (192.168.1.3)] to MAC address d2:0c:37:54:86:c4, Apr 28 12:33:22
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 28 12:10:19
[DHCP IP: (192.168.1.4)] to MAC address ac:cf:5c:28:74:73, Apr 28 12:10:19
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 19:02:58
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 19:02:58
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 18:50:58
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 18:50:58
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 18:26:57
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 18:26:57
[DHCP IP: (192.168.1.5)] to MAC address fe:67:85:ba:43:20, Apr 28 11:19:31
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 18:14:48
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 18:14:48
[DHCP IP: (192.168.1.6)] to MAC address ea:1a:78:f0:e0:19, Apr 28 10:41:51
[DHCP IP: (192.168.1.8)] to MAC address b2:3a:c6:23:aa:0f, Apr 28 10:26:11
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 17:14:48
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 17:14:48
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 17:02:38
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 17:02:38
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 16:50:38
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 16:50:38
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 16:38:37
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 16:38:37
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 16:14:38
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 16:14:38
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 15:38:27
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 15:38:27
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 15:26:27
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 15:26:27
[DHCP IP: (192.168.1.7)] to MAC address 7e:88:74:62:ab:b6, Apr 28 08:25:05
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 15:14:27
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 15:14:27
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 15:02:18
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 15:02:18
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 14:26:17
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 14:26:17
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 14:14:17
[DoS attack: LAND Attack] source: 24.18.228.24, port: 138, Apr 28 14:14:17
[DoS attack: FW.WANATTACK DROP] source: 24.18.228.24, port: 138, Apr 28 14:02:18
Message 3 of 9
FURRYe38
Guru

Re: CAX30 Poor Cable Connection Status

Please post a copy and paste of the modems event log page. This differs from the normal logs. Those are the router logs.

Message 4 of 9
IcedTea
Aspirant

Re: CAX30 Poor Cable Connection Status

 oh sorry, I was on the wrong tab. Here is the event log

TimePriorityDescription
2024-04-30 15:11:14Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:10:58Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:02:27Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:02:21Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:43:05Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:42:51Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:48Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:31Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:24Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:19Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:19Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:16Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:40:59Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:40:58Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:30:52Critical (3)UCD invalid or channel unusable;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:22:29Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:56Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:48Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:46Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:33Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:32Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:57Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:53Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:52Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:52Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:37Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:51Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:42Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:31Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:33Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:26Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:15Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:15Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:12Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:59Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:42Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:21Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:15Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:16:55Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:16:08Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
Message 5 of 9
FURRYe38
Guru

Re: CAX30 Poor Cable Connection Status

Lots of warning entries. Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

 

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-Mod...
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/

Message 6 of 9
IcedTea
Aspirant

Re: CAX30 Poor Cable Connection Status

I already purchased new coax cables and powered off my modem. I'll check in with my ISP about this now, thank you.

Message 7 of 9
IcedTea
Aspirant

Re: CAX30 Poor Cable Connection Status

I talked to my isp and they said “your modem is not capable for the upgraded signals that is the bootfile is getting timed out”, they’re sending an xfinity modem because they said it’ll be compatible. If things go smoothly with the new modem then I’ll just return the CAX30S that I bought.
Message 8 of 9
FURRYe38
Guru

Re: CAX30 Poor Cable Connection Status

The CAX30 Is not on there next gen approved speed list. 

I believe they only support the CAX30 on the 800Mpbs speed package. Something to ask them about. If they can send that config file, the CAX30 should work well. 

 

I don't know if or when the CAX30 could be approved for next gen. We don't get that info. 

If you want next gen speed package support you'll need to get something that's on there support list for this support:

https://community.netgear.com/t5/Cable-Modems-Gateways/ComCast-XFinity-Next-Generation-ISP-FAQ/td-p/...

 

Again, the ISP will need to clear up any issues seen in the Event Log output. 


Good Luck.

 

Message 9 of 9
Top Contributors
Discussion stats
  • 8 replies
  • 669 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi 770 Series