on 18-07-2022 22:32
I have an ongoing problem which results in some days where my connection is completely unreliable. (see bqm below). During these days I can't reliably use streaming media or anything that relies on a stable connection. I have a hub 3.0 in modem mode. I can have weeks where the connection is fine, with almost no loss, then several days with this type of fault.
Virgin have sent out engineers twice and changed cables etc, it looks like a network conflict to me.
Answered! Go to Answer
on 19-07-2022 17:03
@clarki100 wrote:but I don't understand why these would cause the pack loss measured on BQM which is pinging the hub itself?
I said there were several threads on this... there have been over the last year or two - but I forgot to "save" them. However I have stumbled across one old one that has some evidence. See message 12 here...
on 19-07-2022 15:23
on 19-07-2022 16:04
Tanks here goes
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 139000000 | 4.5 | 38 | 256 qam | 1 |
2 | 147000000 | 4.4 | 38 | 256 qam | 2 |
3 | 155000000 | 3.9 | 38 | 256 qam | 3 |
4 | 163000000 | 3.5 | 38 | 256 qam | 4 |
5 | 171000000 | 3.5 | 38 | 256 qam | 5 |
6 | 179000000 | 3.4 | 38 | 256 qam | 6 |
7 | 187000000 | 3.2 | 38 | 256 qam | 7 |
8 | 195000000 | 3 | 38 | 256 qam | 8 |
9 | 203000000 | 2.7 | 38 | 256 qam | 9 |
10 | 211000000 | 2.5 | 38 | 256 qam | 10 |
11 | 219000000 | 2.2 | 38 | 256 qam | 11 |
12 | 227000000 | 2.2 | 38 | 256 qam | 12 |
13 | 235000000 | 2 | 38 | 256 qam | 13 |
14 | 243000000 | 2.2 | 38 | 256 qam | 14 |
15 | 251000000 | 2.2 | 38 | 256 qam | 15 |
16 | 259000000 | 2.4 | 38 | 256 qam | 16 |
17 | 267000000 | 2.2 | 38 | 256 qam | 17 |
18 | 275000000 | 2.2 | 40 | 256 qam | 18 |
19 | 283000000 | 2 | 40 | 256 qam | 19 |
20 | 291000000 | 2 | 38 | 256 qam | 20 |
21 | 299000000 | 1.7 | 38 | 256 qam | 21 |
22 | 307000000 | 1.4 | 38 | 256 qam | 22 |
23 | 315000000 | 1 | 38 | 256 qam | 23 |
24 | 323000000 | 0.7 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 488 | 0 |
2 | Locked | 38.6 | 398 | 0 |
3 | Locked | 38.6 | 498 | 0 |
4 | Locked | 38.6 | 550 | 0 |
5 | Locked | 38.9 | 689 | 1989 |
6 | Locked | 38.9 | 436 | 0 |
7 | Locked | 38.6 | 447 | 0 |
8 | Locked | 38.9 | 407 | 0 |
9 | Locked | 38.6 | 369 | 0 |
10 | Locked | 38.6 | 464 | 0 |
11 | Locked | 38.9 | 553 | 0 |
12 | Locked | 38.9 | 836 | 0 |
13 | Locked | 38.9 | 1105 | 0 |
14 | Locked | 38.9 | 1752 | 0 |
15 | Locked | 38.9 | 1816 | 0 |
16 | Locked | 38.9 | 1557 | 0 |
17 | Locked | 38.9 | 829 | 0 |
18 | Locked | 40.3 | 471 | 0 |
19 | Locked | 40.3 | 633 | 0 |
20 | Locked | 38.9 | 499 | 0 |
21 | Locked | 38.9 | 669 | 0 |
22 | Locked | 38.9 | 635 | 0 |
23 | Locked | 38.9 | 885 | 0 |
24 | Locked | 38.9 | 945 | 0 |
on 19-07-2022 16:04
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 42.8 | 5120 | 64 qam | 8 |
2 | 46200000 | 42.3 | 5120 | 32 qam | 7 |
3 | 60300034 | 45 | 5120 | 64 qam | 5 |
4 | 53700000 | 44.3 | 5120 | 64 qam | 6 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 5 | 0 |
2 | ATDMA | 0 | 0 | 10 | 0 |
3 | ATDMA | 0 | 0 | 4 | 0 |
4 | ATDMA | 0 | 0 | 6 | 0 |
on 19-07-2022 16:06
Time Priority Description
19/07/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2022 09:38:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2022 20:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2022 00:56:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/07/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/07/2022 15:02:5 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/07/2022 20:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/06/2022 13:14:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/06/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/06/2022 11:00:53 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/06/2022 12:02:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2022 20:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/06/2022 13:55:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/06/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2022 04:51:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2022 20:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/06/2022 11:20:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2022 15:49:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/06/2022 08:13:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 19-07-2022 16:09
Thanks again for your response.
FYI, my hub is connected directly to the virgin cable. I do have various downstream switches and hubs, but I don't understand why these would cause the pack loss measured on BQM which is pinging the hub itself?
19-07-2022 16:09 - edited 19-07-2022 16:10
What router model do you have? (not the hub)
Looks like you have something DoS the upstream.
@clarki100 wrote:....pack loss measured on BQM which is pinging the hub itself?
not in modem mode
on 19-07-2022 16:27
I'm using a TP link Deco mesh. Wired connection is:
Hub 3 > first TP link AP > switch > distributed TP link APs and wired devices
on 19-07-2022 16:33
on 19-07-2022 17:03
@clarki100 wrote:but I don't understand why these would cause the pack loss measured on BQM which is pinging the hub itself?
I said there were several threads on this... there have been over the last year or two - but I forgot to "save" them. However I have stumbled across one old one that has some evidence. See message 12 here...