cancel
Showing results for 
Search instead for 
Did you mean: 

Packet Loss

Anonymous
Not applicable

It has been a year that I experience packet loss and unstable connection while gaming. I have (obviously) performed the basic troubleshooting; factory reset, checking hardware equipment, network card, BIOS and driver update etc. I have tested all my equipment (even bought new ones) but Virgin Media is not convinced that the problem is not on my end even a technician has already visited and upgraded the hub and cables inside the property. I don't have any issues with my internet speed and everyday use like video streaming, video calls, browsing etc. or at least not noticeable in doing these tasks except gaming. I do not get continues packet loss while gaming but when I do it is a big lag and honestly it has ruined my gaming experience.

So here is the technical stuff and just to mention my hub is on modem mode and I use the Asus Rog gaming router.

6 REPLIES 6

Anonymous
Not applicable

Network Log

Time Priority Description

Thu 18/07/2024
11:55:30
6CM-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;
Thu 18/07/2024
02:13:54
6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/07/2024
02:13:54
5DBC-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;
Thu 18/07/2024
02:03:47
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/07/2024
02:03:47
5DBC-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;
Thu 18/07/2024
01:33:38
6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/07/2024
01:33:38
5DBC-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;
Thu 18/07/2024
01:33:20
6CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/07/2024
01:33:20
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970
00:01:22
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/07/2024
09:45:54
6CM-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;
Wed 17/07/2024
01:41:31
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/07/2024
01:41:31
5DBC-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;
Wed 17/07/2024
01:31:22
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/07/2024
01:21:18
5DBC-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;
Wed 17/07/2024
01:11:12
6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/07/2024
01:11:12
5DBC-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;
Wed 17/07/2024
01:10:56
6CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/07/2024
01:10:55
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970
00:01:23
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
21:23:17
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
21:23:17
5DBC-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;
Tue 16/07/2024
19:48:19
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
05:15:44
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
03:06:10
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
01:53:56
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
01:53:56
5DBC-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;
Tue 16/07/2024
01:43:48
6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
01:43:31
6CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/07/2024
01:43:30
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970
00:01:19
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/07/2024
19:41:48
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/07/2024
19:29:33
6DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/07/2024
19:29:33
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/07/2024
10:07:55
6CM-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;
Mon 15/07/2024
07:38:37
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/07/2024
07:38:37
5DBC-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;
Sun 14/07/2024
23:22:03
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/07/2024
23:22:03
5DBC-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;
Sun 14/07/2024
16:28:49
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/07/2024
16:28:49
5DBC-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;
Sun 14/07/2024
16:18:45
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/07/2024
16:18:45
5DBC-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;
Sat 13/07/2024
13:55:24
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 13/07/2024
13:55:24
5DBC-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;
Sat 13/07/2024
13:45:17
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 13/07/2024
13:45:17
5DBC-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;
Sat 13/07/2024
02:59:53
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 13/07/2024
01:14:54
6DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 13/07/2024
01:14:53
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Anonymous
Not applicable

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

25331000000-0.137.4QAM25625
11390000005.737.6QAM2561
2147000000537.6QAM2562
31550000004.337.6QAM2563
4163000000437.6QAM2564
51710000003.537.6QAM2565
6179000000337.6QAM2566
71870000002.537.4QAM2567
8195000000237.4QAM2568
92030000001.837.6QAM2569
122270000000.736.6QAM25612
132350000000.437.4QAM25613
14243000000-0.237.4QAM25614
15251000000-0.936.6QAM25615
16259000000-0.536.6QAM25616
17267000000-0.137.4QAM25617
18275000000-0.236.6QAM25618
19283000000-0.437.4QAM25619
20291000000-0.437.4QAM25620
21299000000-0.137.4QAM25621
22307000000037.6QAM25622
23315000000-0.437.4QAM25623
24323000000037.4QAM25624
263390000000.237.4QAM25626
27347000000-0.237.6QAM25627
28355000000-1.437.4QAM25628
29363000000-137.4QAM25629
30371000000-137.4QAM25630
31379000000-1.137.4QAM25631
32387000000-1.237.4QAM25632
34403000000-0.937.6QAM25634
35411000000-0.537.6QAM25635



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked37.35598800
1Locked37.63627600
2Locked37.63627600
3Locked37.63627600
4Locked37.63627600
5Locked37.63627600
6Locked37.63627600
7Locked37.35598800
8Locked37.35598800
9Locked37.63627600
12Locked36.60965300
13Locked37.35598800
14Locked37.35598800
15Locked36.60965300
16Locked36.60965300
17Locked37.35598800
18Locked36.60965300
19Locked37.35598800
20Locked37.35598800
21Locked37.35598800
22Locked37.63627600
23Locked37.35598800
24Locked37.35598800
26Locked37.35598800
27Locked37.63627600
28Locked37.35598800
29Locked37.35598800
30Locked37.35598800
31Locked37.35598800
32Locked37.35598800
34Locked37.63627600
35Locked37.63627600



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1840QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked35-10.2380224296497

Anonymous
Not applicable

BQM

BQM_1.jpgBQM_2.jpg

Hi Legacy5618,

Thanks for posting and welcome to our community  😊

Sorry to see you're having connection issues. We're limited to what we can do whilst you're using a 3rd part router. 

Can you confirm if you experience these problems when the hub is in router mode?

Alex_Rm

Anonymous
Not applicable

Thanks for your reply,

I confirm that I still experience the same problem when the hub is in router mode, tested using both wired and wireless.

You're welcome, sorry to see that you're still seeing issues with this.

We've checked our system and can see that everything looks as it should do. We're happy to do some further checks to see why you're having these issues.

I'll pop you a PM to confirm your details so this can be done.

Regards

Nathan

The do's and don'ts. Keep the community welcoming for all. Follow the house rules