User Profile

Swinder

Up to speed

Joined 16 years ago

175 Posts4 Solutions

View All Badges

User Widgets

Contributions

Re: Regular Packet Loss Causing Disconnects
3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 46 5120 QAM 64 1 1 43100000 46.5 5120 QAM 64 2 2 36600000 45.8 5120 QAM 64 3 3 30100000 45.5 5120 QAM 64 4 4 23600000 45 5120 QAM 64 5 3.0 Upstream channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0 ATDMA 0 0 4 0 1 ATDMA 0 0 4 0 2 ATDMA 0 0 16 0 3 ATDMA 0 0 6 0 4 ATDMA 0 0 7 0 3.1 Upstream channels Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation 6 10 39.7 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 1 0
1 month ago Place Gaming Support
21Views
0likes
0Comments
Re: Regular Packet Loss Causing Disconnects
3.0 Downstream channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 331000000 6 41 QAM 256 25 2 139000000 7.6 40 QAM 256 1 3 163000000 7 40 QAM 256 4 4 171000000 6.6 40 QAM 256 5 5 179000000 6.6 40 QAM 256 6 6 195000000 6.6 40 QAM 256 8 7 203000000 6.7 40 QAM 256 9 8 227000000 6.3 40 QAM 256 12 9 235000000 6.2 40 QAM 256 13 10 259000000 6.1 40 QAM 256 16 11 267000000 5.9 40 QAM 256 17 12 275000000 5.5 40 QAM 256 18 13 283000000 5.4 40 QAM 256 19 14 291000000 5.4 40 QAM 256 20 15 299000000 5.5 40 QAM 256 21 16 307000000 6 41 QAM 256 22 17 315000000 6.1 41 QAM 256 23 18 323000000 5.9 41 QAM 256 24 19 339000000 6 41 QAM 256 26 20 347000000 6 41 QAM 256 27 21 355000000 6 41 QAM 256 28 22 363000000 5.8 41 QAM 256 29 23 371000000 5.9 41 QAM 256 30 24 379000000 5.8 41 QAM 256 31 25 387000000 5.6 41 QAM 256 32 26 395000000 5.6 41 QAM 256 33 27 403000000 5.3 41 QAM 256 34 28 411000000 5.3 41 QAM 256 35 29 419000000 5.2 41 QAM 256 36 30 427000000 4.8 40 QAM 256 37 31 435000000 4.8 40 QAM 256 38 32 443000000 4.5 40 QAM 256 39 3.0 Downstream channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 41 993 25 2 Locked 40 5992153 312183 3 Locked 40 3450941 182491 4 Locked 40 5611508 299239 5 Locked 40 8142892 311652 6 Locked 40 4898 69 7 Locked 40 4151 57 8 Locked 40 3208 52 9 Locked 40 2884 45 10 Locked 40 1868 37 11 Locked 40 1667 39 12 Locked 40 2286535 205068 13 Locked 40 870467 91588 14 Locked 40 2345 40 15 Locked 40 2105 28 16 Locked 41 3642 80 17 Locked 41 3522 37 18 Locked 41 1048 14 19 Locked 41 2140 30 20 Locked 41 1925 61 21 Locked 41 920 30 22 Locked 41 948 14 23 Locked 41 856 0 24 Locked 41 916 14 25 Locked 41 905 7 26 Locked 41 873 0 27 Locked 41 895 7 28 Locked 41 844 12 29 Locked 41 891 0 30 Locked 40 852 0 31 Locked 40 909 2 32 Locked 40 902 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 0 1.5 238052924 135
1 month ago Place Gaming Support
2Views
0likes
1Comment
Re: Regular Packet Loss Causing Disconnects
Hi Robert. The device is in router mode and has been since the 20th December. Apologies for any confusion, I thought I had already switched back to modem mode but I must have dreamt it. Below is what we have seen today so far, the vast majority of these are causing disconnects to game services, workplace VPN's or a brief but noticeable slow down of general browsing. You can also see they are increasing in frequency... Time Priority Description 29/01/2026 13:20 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 13:20 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 13:20 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 13:20 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:49 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:49 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:49 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:49 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:19 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:19 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:18 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 12:18 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:48 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:48 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:47 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:47 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:17 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:17 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:16 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 11:16 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:46 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:46 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:45 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:45 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:15 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:15 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:15 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:15 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 10:13 warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 09:44 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 29/01/2026 09:44 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
1 month ago Place Gaming Support
16Views
0likes
2Comments
Re: Regular Packet Loss Causing Disconnects
A correction, the device is already in router mode. I hadn't switched it back to modem mode after going through the last lot of testing. It has now been in router mode since 20th December. As a bit of info from the log, here is a snippet of a very frequent error message in the network log. These occur every 58 minutes past and appear to coincide with the spikes in the packet loss. The error is adjusted a little due to mac addresses being present. 26-01-2026 12:58:36 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; 26-01-2026 12:58:36 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1; and a little less frequent but still somewhat common... 26-01-2026 09:54:10 warning Dynamic Range Window violation 26-01-2026 09:54:10 warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
1 month ago Place Gaming Support
44Views
0likes
0Comments
Re: Regular Packet Loss Causing Disconnects
Hi Nathan, thanks for your reply. The hub is currently in modem mode but this issue persists in router mode as well so I am fairly convinced that the kit post the point of the modem is fine. As a test, I have connected wirelessly to my works provided 5g modem and I can't replicate the issues on any device when connected to that network. Below is as of today and it has been worse over the weekend just gone. I'll switch into router mode at some point this afternoon as you've requested but, as already mentioned, it does persist through both modes. Does the input that legacy1 has kindly shared identify anything?
1 month ago Place Gaming Support
57Views
0likes
5Comments
Re: Regular Packet Loss Causing Disconnects
Still no improvement. The frequency of disconnects are increasing again and are most notable during peak hours. You'll have no issues and then you will have 5-10mins of high latency with disconnects. More severe latency/disconnects coincide with the packet lost spikes. I am still in modem mode, the 2 affected devices are both wired, have replaced all ethernet cables and swapped out the coax for another VM spare I had.
2 months ago Place Gaming Support
93Views
0likes
7Comments
Re: Regular Packet Loss Causing Disconnects
Apologies for the delayed response. The connection is about the same, though straight disconnects appear to be less frequent. Packet loss is still present. I am still in router mode so I am confident that issues stem from the modem backwards rather than with my local setup. It impacts two separate wired desktop PC regardless of modem/router mode and both have had their lan cables replaced since the issue. Coax from the wall box to modem has also been checked with a spare from a previous install, no change there.
2 months ago Place Gaming Support
118Views
0likes
1Comment
Re: Regular Packet Loss Causing Disconnects
Just to bump this. The connection has improved a little since switched to router mode, but is likely a coincidence rather than indicating an issue with my 3rd party router. There was a bit of what looked like local utilisation issues due to Christmas which has susbsided for now but the packet loss is still present and, whilst not spiking and causing disconnects as often, it is clearly become more frequent rather than consistent intervals.
2 months ago Place Gaming Support
134Views
0likes
3Comments
Regular Packet Loss Causing Disconnects
Since 1st November I have seen regular spikes of packet loss, initially small and not causing any increased latency or disconnects Progressively this has worsened to the point that the packet loss spikes are virtually on the hour, every hour and are far more noticeable whilst gaming. These spikes coincide with disconnects from World of Warcraft on two different desktop PC's. Above is for 16th December as 17th I turned "allow ping from WAN" off via my Flint 2 router to test as I have heard of regular timed tests (Samknows) causing issues for others. This hasn't fixed my issue. The issue persists via modem mode into a Flint 2 router as well as via the router mode on the modem itself. Impacted desktops are wired but I haven't tested wireless as I am confident this issue will persist. I'll drop the logs in a reply below.
3 months ago Place Gaming Support
405Views
0likes
20Comments
Re: Severe Packet Loss (Area04)
Thanks for the info, will keep that number handy as the web driven status frequently crashes out for me. Regarding the packet loss, I lost the connection completely for ~45mins then it cam back completely free from packet loss so who knows what was fixed or was the cause for it.... Ignore the 4am loss, that is my scheduled router restart.
1 year ago Place Managing Your Account - Cable
273Views
0likes
0Comments