Menu
Reply
ConnorLinfoot
  • 3
  • 0
  • 0
Joining in
528 Views
Message 1 of 3
Flag for a moderator

Incoming Packet Loss

Hello,

I've recently been having an issue where randomly my connection will have bad incoming packet loss. When using something such as TeamSpeak my outgoing packets are completely fine but incoming goes up to 50% packet loss and is not usable. You can see the below which is a ping to 1.1.1.1 and packets being missing or response being much higher than the usual ~10ms.

PING 1.1.1.1 (1.1.1.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=545.922 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=537.047 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=513.490 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 1.1.1.1: icmp_seq=6 ttl=58 time=362.793 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=58 time=459.233 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=58 time=536.557 ms
Request timeout for icmp_seq 9
64 bytes from 1.1.1.1: icmp_seq=10 ttl=58 time=565.571 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=58 time=337.862 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=58 time=553.500 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=58 time=632.025 ms
64 bytes from 1.1.1.1: icmp_seq=14 ttl=58 time=224.311 ms
Request timeout for icmp_seq 15
64 bytes from 1.1.1.1: icmp_seq=16 ttl=58 time=296.900 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=58 time=414.770 ms
Request timeout for icmp_seq 18
64 bytes from 1.1.1.1: icmp_seq=19 ttl=58 time=525.102 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=58 time=395.037 ms
64 bytes from 1.1.1.1: icmp_seq=21 ttl=58 time=415.464 ms
64 bytes from 1.1.1.1: icmp_seq=22 ttl=58 time=255.357 ms
64 bytes from 1.1.1.1: icmp_seq=23 ttl=58 time=507.085 ms
64 bytes from 1.1.1.1: icmp_seq=24 ttl=58 time=468.277 ms
64 bytes from 1.1.1.1: icmp_seq=25 ttl=58 time=451.432 ms
64 bytes from 1.1.1.1: icmp_seq=26 ttl=58 time=641.319 ms
64 bytes from 1.1.1.1: icmp_seq=27 ttl=58 time=602.123 ms
64 bytes from 1.1.1.1: icmp_seq=28 ttl=58 time=607.257 ms
64 bytes from 1.1.1.1: icmp_seq=29 ttl=58 time=553.320 ms
64 bytes from 1.1.1.1: icmp_seq=30 ttl=58 time=507.133 ms
64 bytes from 1.1.1.1: icmp_seq=31 ttl=58 time=477.712 ms
64 bytes from 1.1.1.1: icmp_seq=32 ttl=58 time=561.105 ms
64 bytes from 1.1.1.1: icmp_seq=33 ttl=58 time=596.479 ms
64 bytes from 1.1.1.1: icmp_seq=34 ttl=58 time=610.499 ms
64 bytes from 1.1.1.1: icmp_seq=35 ttl=58 time=462.864 ms
64 bytes from 1.1.1.1: icmp_seq=36 ttl=58 time=460.558 ms
64 bytes from 1.1.1.1: icmp_seq=37 ttl=58 time=351.356 ms
64 bytes from 1.1.1.1: icmp_seq=38 ttl=58 time=432.714 ms
64 bytes from 1.1.1.1: icmp_seq=39 ttl=58 time=466.551 ms
64 bytes from 1.1.1.1: icmp_seq=40 ttl=58 time=386.577 ms
64 bytes from 1.1.1.1: icmp_seq=41 ttl=58 time=456.878 ms
64 bytes from 1.1.1.1: icmp_seq=42 ttl=58 time=241.420 ms
64 bytes from 1.1.1.1: icmp_seq=43 ttl=58 time=13.077 ms
64 bytes from 1.1.1.1: icmp_seq=44 ttl=58 time=11.735 ms

I also use the Virgin Hub in modem mode and when this occurs I notice the connection of the Virgin Hub to my modem also completely stops working and it gets 0 ping responses back during the issue.

64 bytes from 192.168.100.1: icmp_seq=2464 ttl=63 time=1.580 ms
64 bytes from 192.168.100.1: icmp_seq=2465 ttl=63 time=1.868 ms
64 bytes from 192.168.100.1: icmp_seq=2466 ttl=63 time=2.024 ms
64 bytes from 192.168.100.1: icmp_seq=2467 ttl=63 time=1.510 ms
64 bytes from 192.168.100.1: icmp_seq=2468 ttl=63 time=1.964 ms
64 bytes from 192.168.100.1: icmp_seq=2469 ttl=63 time=2.214 ms
64 bytes from 192.168.100.1: icmp_seq=2470 ttl=63 time=2.399 ms
64 bytes from 192.168.100.1: icmp_seq=2471 ttl=63 time=1.676 ms
Request timeout for icmp_seq 2472
Request timeout for icmp_seq 2473
Request timeout for icmp_seq 2474
Request timeout for icmp_seq 2475
Request timeout for icmp_seq 2476
Request timeout for icmp_seq 2477
Request timeout for icmp_seq 2478
Request timeout for icmp_seq 2479
Request timeout for icmp_seq 2480
Request timeout for icmp_seq 2481
Request timeout for icmp_seq 2482
Request timeout for icmp_seq 2483
Request timeout for icmp_seq 2484
Request timeout for icmp_seq 2485
Request timeout for icmp_seq 2486
Request timeout for icmp_seq 2487
Request timeout for icmp_seq 2488
Request timeout for icmp_seq 2489
Request timeout for icmp_seq 2490
Request timeout for icmp_seq 2491
Request timeout for icmp_seq 2492
Request timeout for icmp_seq 2493
Request timeout for icmp_seq 2494
Request timeout for icmp_seq 2495
Request timeout for icmp_seq 2496
Request timeout for icmp_seq 2497
Request timeout for icmp_seq 2498
Request timeout for icmp_seq 2499
Request timeout for icmp_seq 2500
Request timeout for icmp_seq 2501
Request timeout for icmp_seq 2502
Request timeout for icmp_seq 2503
Request timeout for icmp_seq 2504
Request timeout for icmp_seq 2505
Request timeout for icmp_seq 2506
Request timeout for icmp_seq 2507
Request timeout for icmp_seq 2508
Request timeout for icmp_seq 2509
Request timeout for icmp_seq 2510
Request timeout for icmp_seq 2511
Request timeout for icmp_seq 2512
Request timeout for icmp_seq 2513
Request timeout for icmp_seq 2514
Request timeout for icmp_seq 2515
Request timeout for icmp_seq 2516
Request timeout for icmp_seq 2517
Request timeout for icmp_seq 2518
Request timeout for icmp_seq 2519
Request timeout for icmp_seq 2520
Request timeout for icmp_seq 2521
Request timeout for icmp_seq 2522
Request timeout for icmp_seq 2523
Request timeout for icmp_seq 2524
Request timeout for icmp_seq 2525
Request timeout for icmp_seq 2526
Request timeout for icmp_seq 2527
Request timeout for icmp_seq 2528
Request timeout for icmp_seq 2529
Request timeout for icmp_seq 2530
Request timeout for icmp_seq 2531
64 bytes from 192.168.100.1: icmp_seq=2532 ttl=63 time=2.053 ms
64 bytes from 192.168.100.1: icmp_seq=2533 ttl=63 time=1.591 ms

I've also attached a BQM below where you can see when the issue occured last with a large spike in packet loss. I have also tried the some of the usual steps to fix the issue, rebooting the hub, switching out the cables, and making sure they're all connected fully, etc. My connection is also wired so WiFi is not an issue.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/80945a55b910638df711235220bb2cba91a127e2-18-07-2020

 

Any help would be appreciated!

0 Kudos
Reply
ConnorLinfoot
  • 3
  • 0
  • 0
Joining in
506 Views
Message 2 of 3
Flag for a moderator

Re: Incoming Packet Loss

To add more info if needed from the hub:

Firmware: 9.1.1811.401

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 331000000 -2.2 40 256 qam 25
2 267000000 -1.2 40 256 qam 17
3 275000000 -1.5 40 256 qam 18
4 283000000 -1.5 40 256 qam 19
5 291000000 -1.7 40 256 qam 20
6 299000000 -2 40 256 qam 21
7 307000000 -1.9 40 256 qam 22
8 315000000 -2 40 256 qam 23
9 323000000 -2.5 40 256 qam 24
10 339000000 -2.7 40 256 qam 26
11 347000000 -2.5 40 256 qam 27
12 355000000 -3.2 40 256 qam 28
13 363000000 -3 40 256 qam 29
14 371000000 -3.2 40 256 qam 30
15 379000000 -3.7 38 256 qam 31
16 387000000 -3.7 40 256 qam 32
17 395000000 -3.7 40 256 qam 33
18 403000000 -4 40 256 qam 34
19 411000000 -3.7 40 256 qam 35
20 419000000 -4 40 256 qam 36
21 427000000 -4 40 256 qam 37
22 435000000 -4.5 40 256 qam 38
23 443000000 -4.7 40 256 qam 39
24 451000000 -4.9 40 256 qam 40


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 306 55
2 Locked 40.3 4409 115
3 Locked 40.3 2757 64
4 Locked 40.9 1823 91
5 Locked 40.9 1384 45
6 Locked 40.3 981 156
7 Locked 40.3 572 43
8 Locked 40.3 474 12
9 Locked 40.9 372 41
10 Locked 40.9 300 58
11 Locked 40.9 205 65
12 Locked 40.3 204 67
13 Locked 40.3 131 47
14 Locked 40.9 135 52
15 Locked 38.6 133 7
16 Locked 40.3 134 25
17 Locked 40.3 108 10
18 Locked 40.3 107 45
19 Locked 40.3 109 26
20 Locked 40.3 109 93
21 Locked 40.3 93 23
22 Locked 40.3 80 24
23 Locked 40.3 74 40
24 Locked 40.9 105 35

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 4.15 5120 64 qam 10
2 25800000 3.95 5120 64 qam 12
3 32600000 4.125 5120 64 qam 11
4 46200000 4.25 5120 64 qam 9


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

Network Log
Time Priority Description
18/07/2020 10:51:32 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 14:21:4 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 14:21:4 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:42:58 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:42:57 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:41:22 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:41:21 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:40:13 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:39:39 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.0;
17/07/2020 01:39:35 critical DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:38:15 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:38:12 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:36:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:36:20 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:34:29 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:19: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.0;
17/07/2020 01:19:9 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:19:4 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:19:3 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2020 01:19:3 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
Zoie_P
  • 2.13K
  • 97
  • 165
Forum Team
Forum Team
415 Views
Message 3 of 3
Flag for a moderator

Re: Incoming Packet Loss

Hi ConnorLinfoot,

Thank you for your post 🙂
I am sorry you are having some issues, I have checked and there are some issues, I will pop you over a private message and I can look into this for you 🙂

Thanks,

Zoie

0 Kudos
Reply