Menu
Reply
Mellors111
  • 4
  • 0
  • 0
Joining in
619 Views
Message 1 of 6
Flag for a moderator

High packet loss, unusable

Don't think this one needs many words. High packet loss started Thursday 29th Sept and has been like this most days since then. It'll occasionally and suddenly sort itself out and go back to normal for a day before becoming almost unusable again. 

VPN struggles to stay connected for more than a few minutes when there's high packet loss, online gaming is impossible as match making won't work and when it does I get disconnected within seconds of joining. 

Hub has been rebooted and reset by pressing the pinhole in.

October 5th

October 6th

October 7th

October 8th (My work VPN stayed connected for a few hours this afternoon woo)

Today (9th)

Speedtests both with wired connection. It'll go full speed then slow to a crawl during the test for both upload and download. 

Ping test from the router to virginmedia.com

PING virginmedia.com (213.105.9.24): 64 data bytes
72 bytes from 213.105.9.24: seq=0 ttl=247 time=20.000 ms
72 bytes from 213.105.9.24: seq=1 ttl=247 time=10.000 ms
72 bytes from 213.105.9.24: seq=2 ttl=247 time=3950.000 ms
72 bytes from 213.105.9.24: seq=3 ttl=247 time=6710.000 ms
72 bytes from 213.105.9.24: seq=4 ttl=247 time=10790.000 ms
72 bytes from 213.105.9.24: seq=5 ttl=247 time=12560.000 ms
72 bytes from 213.105.9.24: seq=7 ttl=247 time=12360.000 ms
72 bytes from 213.105.9.24: seq=9 ttl=247 time=12160.000 ms
72 bytes from 213.105.9.24: seq=10 ttl=247 time=12330.000 ms
72 bytes from 213.105.9.24: seq=11 ttl=247 time=12550.000 ms
72 bytes from 213.105.9.24: seq=13 ttl=247 time=13030.000 ms
72 bytes from 213.105.9.24: seq=14 ttl=247 time=13220.000 ms
72 bytes from 213.105.9.24: seq=15 ttl=247 time=13300.000 ms
72 bytes from 213.105.9.24: seq=16 ttl=247 time=13350.000 ms
72 bytes from 213.105.9.24: seq=17 ttl=247 time=13590.000 ms
72 bytes from 213.105.9.24: seq=18 ttl=247 time=12480.000 ms
72 bytes from 213.105.9.24: seq=19 ttl=247 time=12350.000 ms
72 bytes from 213.105.9.24: seq=20 ttl=247 time=12410.000 ms
72 bytes from 213.105.9.24: seq=21 ttl=247 time=12540.000 ms
72 bytes from 213.105.9.24: seq=22 ttl=247 time=13010.000 ms
72 bytes from 213.105.9.24: seq=23 ttl=247 time=12420.000 ms
--- virginmedia.com ping statistics ---
30 packets transmitted, 21 packets received, 30% packet loss
round-trip min/avg/max = 10.000/10720.952/13590.000 ms

0 Kudos
Reply
Mellors111
  • 4
  • 0
  • 0
Joining in
617 Views
Message 2 of 6
Flag for a moderator

Re: High packet loss, unusable

Downstream bonded channels

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

132300000011.438256 qam24
22030000009.538256 qam9
3211000000938256 qam10
42190000008.938256 qam11
52270000008.838256 qam12
62350000008.538256 qam13
72430000008.138256 qam14
82510000008.638256 qam15
92590000009.538256 qam16
1026700000010.438256 qam17
1127500000010.438256 qam18
1228300000010.638256 qam19
1329100000010.838256 qam20
1429900000010.838256 qam21
1530700000010.938256 qam22
1631500000011.338256 qam23
1733100000011.138256 qam25
183710000009.938256 qam26
193790000001038256 qam27
2038700000010.138256 qam28
2139500000010.138256 qam29
2240300000010.338256 qam30
234110000001138256 qam31
244190000001138256 qam

32

 

Downstream bonded channels

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

1Locked38.950
2Locked38.660
3Locked38.650
4Locked38.650
5Locked38.640
6Locked38.640
7Locked38.600
8Locked38.910
9Locked38.650
10Locked38.960
11Locked38.930
12Locked38.950
13Locked38.930
14Locked38.940
15Locked38.650
16Locked38.950
17Locked38.9140
18Locked38.610
19Locked38.6130
20Locked38.670
21Locked38.9120
22Locked38.680
23Locked38.6160
24Locked38.900
0 Kudos
Reply
Mellors111
  • 4
  • 0
  • 0
Joining in
616 Views
Message 3 of 6
Flag for a moderator

Re: High packet loss, unusable

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1462000004.225512064 qam9
2258000003.975512064 qam12
3326000004.075512064 qam11
4394000004.175512064 qam10

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

Network Log

Time Priority Description

09/10/2020 20:53:58noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 20:53:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 20:45:25noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 02:43:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 17:21:12noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 17:21:12ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 17:21:9ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 07:36:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 07:36:43criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 07:35:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 07:35:24criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 03:02:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2020 03:02:10criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2020 06:44:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2020 06:44:6criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2020 04:34:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2020 04:34:38criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2020 22:31:13criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2020 22:31:13criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2020 22:29:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;



0 Kudos
Reply
Anonymous
Not applicable
550 Views
Message 4 of 6
Flag for a moderator

Re: High packet loss, unusable

The downstream power levels are out of spec on most of your channels (-6 to +10 is in spec).

0 Kudos
Reply
Mellors111
  • 4
  • 0
  • 0
Joining in
513 Views
Message 5 of 6
Flag for a moderator

Re: High packet loss, unusable

After many attempts I finally got through to an actual person on the phone to be told there is a known issue in the area that has fix date of October 19th. So nothing will be done with regards to that until the other fault is fixed. 

Spotted that the upstream modulation flaps between 16, 32 and 64. It's when it goes from 64 to 32 that the connection drops for 10 or so seconds.

And past experience tells me that the October 19th fix date won't be the original fix date and most certainly will get delayed further. 

0 Kudos
Reply
Chris_W1
  • 4.06K
  • 185
  • 255
Forum Team
Forum Team
446 Views
Message 6 of 6
Flag for a moderator

Re: High packet loss, unusable

Hi Mellors111, thanks for the message and sorry to hear that you are having issues with the broadband connection. Can you confirm if the issues have now been resolved? Has the fix time been updated? Do you have an updated BQM? Chris 

0 Kudos
Reply