cfreeman
Tuning in
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Bad Routing?
There was 100% packet loss on hop 4, significant packet loss on hop 5, the latency start low 0.5 but increases significantly by hop 3. With VPN on 0% packet loss. Latency is slightly higher but consistent across all hops but im sure that is normal using a VPN. Also doesn't ChatGPT know a lot?.. "ChatGPT and our other services are developed using (1) information that is publicly available on the internet, (2) information that we partner with third parties to access, and (3) information that our users or human trainers and researchers provide or generate." ChatGPT isn't just making up random answers surely?Bad Routing?
Hello, i have had issues in call of duty for years, feeling like i am half a second behind everyone else in the game. Some very rare times it feels fine but its like 1 in 50 games is good. I asked ChatGPT to analyse my pingplotter to cloudflare (1.1.1.1) without a VPN and with a VPN to determine if bad routing is a potential issue. ChatGPT said it is definitely bad routing. Im not very familiar with networking but can routing be changed? everything else the internet is fine for what we use it for TV/Phones/IPad's but when gaming its horrendous. Ping is relatively low (around 15-17 when lowest and connected to closest server) but it does seem like i have bad routing and/or congestion. My VMHUB5 has lots of T3 timeouts and lots of post/pre RS errors when in router mode, when in modem mode using my NETDUMA R3 it is just Pre RS errors that are on the logs. My power levels was near the limits even with an attenuator but definitely seems better without the attenuator so that has been taken off and power levels just over limit on upstream and downstream. I have posted in these forums numerous times with these issues and nothing ever gets fixed, it didn't bother me for a while because i stopped playing call of duty so wasn't affecting me but now i have started to play again and it is unplayable alot of the time. Please do not reply with some generic answers about restarting router etc. I have tried everything this has been happening for years since 2019 when i first noticed it playing Warzone 1. Thank you.Re: 2 engineer visits and still issues
Time Priority Description 28-02-2024 20:45:44 notice GUI Login Status - Login Success from LAN interface 28-02-2024 13:32:59 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 28-02-2024 13:32:59 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 28-02-2024 13:22:53 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 28-02-2024 13:22:53 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 28-02-2024 09:32:16 notice GUI Login Status - Login Success from LAN interface 27-02-2024 11:09:29 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 09:54:45 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 09:51:29 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 05:03:34 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 05:00:57 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 02:45:05 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-02-2024 02:42:50 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 12:11:19 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 12:09:36 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:48:09 notice GUI Login Status - Login Success from LAN interface 26-02-2024 10:47:57 notice GUI Login Status - Login Success from LAN interface 26-02-2024 10:45:27 notice GUI Login Status - Login Success from LAN interface 26-02-2024 10:41:34 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:04 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:04 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-Q 26-02-2024 10:41:04 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 13 14 15 16 17 18 19 20 21 22 23 24 26 27 30 31 35 38 39 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:04 notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:03 warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:03 warning Dynamic Range Window violation 26-02-2024 10:41:02 warning Dynamic Range Window violation 26-02-2024 10:41:02 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:02 warning RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:41:02 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:40:52 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:40:52 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 10:40:48 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 06:52:23 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 06:52:23 critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 06:48:24 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 03:54:40 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 26-02-2024 03:52:46 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 25-02-2024 21:44:28 notice GUI Login Status - Login Success from LAN interface2 engineer visits and still issues
I have had 2 engineers come and check why my internet keeps dropping, packet loss and lots of errors. The first time he added a 6db attenuator, second engineer changed the box on the wall and the metal box inside (still had telewest) and changed the attenuator to a 3db one. I am still having issues getting lots of pre/post rs errors and lots of T2/T3/T4 errors. 3.0 Downstream channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 331000000 7.9 41 QAM 256 25 2 139000000 9 41 QAM 256 1 3 147000000 8.9 41 QAM 256 2 4 155000000 8.9 41 QAM 256 3 5 227000000 8.4 41 QAM 256 12 6 235000000 8 41 QAM 256 13 7 243000000 7.9 41 QAM 256 14 8 251000000 7.6 41 QAM 256 15 9 259000000 7.6 40 QAM 256 16 10 267000000 7.5 41 QAM 256 17 11 275000000 7.7 41 QAM 256 18 12 283000000 7.7 40 QAM 256 19 13 291000000 7.7 40 QAM 256 20 14 299000000 7.6 40 QAM 256 21 15 307000000 7.7 40 QAM 256 22 16 315000000 7.8 40 QAM 256 23 17 323000000 7.8 41 QAM 256 24 18 339000000 8 40 QAM 256 26 19 347000000 8.1 40 QAM 256 27 20 355000000 8.1 41 QAM 256 28 21 363000000 8.3 41 QAM 256 29 22 371000000 8.3 41 QAM 256 30 23 379000000 8.3 41 QAM 256 31 24 387000000 8.3 41 QAM 256 32 25 395000000 8 41 QAM 256 33 26 403000000 7.9 41 QAM 256 34 27 411000000 7.7 41 QAM 256 35 28 419000000 7.4 41 QAM 256 36 29 427000000 7.1 41 QAM 256 37 30 435000000 7.2 41 QAM 256 38 31 443000000 7.1 41 QAM 256 39 32 451000000 7 40 QAM 256 40 3.0 Downstream channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 41 205 50 2 Locked 41 90 32 3 Locked 41 85 37 4 Locked 41 99 94 5 Locked 41 129 87 6 Locked 41 140 44 7 Locked 41 154 34 8 Locked 41 206 96 9 Locked 40 225 44 10 Locked 41 202 53 11 Locked 41 180 94 12 Locked 40 248 88 13 Locked 40 265 33 14 Locked 40 270 89 15 Locked 40 273 34 16 Locked 40 234 46 17 Locked 41 228 13 18 Locked 40 245 0 19 Locked 40 235 81 20 Locked 41 227 13 21 Locked 41 223 83 22 Locked 41 170 0 23 Locked 41 199 78 24 Locked 41 193 139 25 Locked 41 179 0 26 Locked 41 184 0 27 Locked 41 165 0 28 Locked 41 187 0 29 Locked 41 191 0 30 Locked 41 167 0 31 Locked 41 182 0 32 Locked 40 137 0 3.1 Downstream channels Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 159 94 4K 1840 QAM 4096 1108 3.1 Downstream channels Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile) 159 Locked 38 5.8 95868817 1374 3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 46.3 5120 QAM 64 1 1 43100000 45.8 5120 QAM 64 2 2 36600000 45.8 5120 QAM 64 3 3 30100000 45.3 5120 QAM 64 4 4 23600000 44.3 5120 QAM 64 5 3.0 Upstream channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0 ATDMA 0 1 4 0 1 ATDMA 0 1 0 0 2 ATDMA 0 1 0 0 3 ATDMA 0 1 0 0 4 ATDMA 0 1 34 2 3.1 Upstream channels Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation 6 10 40.2 2K QAM 256 3.1 Upstream channels Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 6 OFDMA 200 74000000 0 0
