Menu
Reply
FBW
  • 6
  • 0
  • 1
Tuning in
219 Views
Message 1 of 9
Flag for a moderator

Packet loss / drop outs

Recently (around a week and a half ago) I've been having issues with my internet. I've had a look at a few posts in the forum, but I'm afraid I've run into no luck.

I've got the SH3 in Modem mode, and have for over 2 years without issues.

PROBLEM
When gaming, or Zooming, or doing anything that really requires a real-time connection I experience a temporary loss of service. Everything freezes and it takes 15 seconds or so (sometimes longer) to return back.

There have been no devices that have been added to my home, nor has there been any patterns of usage.

I have tried rebooting the router. Tried a pin-hole reset and still no luck.

I have also tried an Ethernet cable to rule out wifi.

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
330750000
Locked
Ranged Upstream Channel (Hz)
32600000
Locked
Provisioning State
Online




0 Kudos
Reply
FBW
  • 6
  • 0
  • 1
Tuning in
218 Views
Message 2 of 9
Flag for a moderator

Re: Packet loss / drop outs

Downstream bonded channels

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

13307500005.338256 qam25
22347500004.538256 qam13
32427500004.438256 qam14
42507500004.838256 qam15
52587500005.338256 qam16
62667500005.338256 qam17
72747500005.438256 qam18
8282750000540256 qam19
92907500005.438256 qam20
102987500005.138256 qam21
113067500005.140256 qam22
123147500005.138256 qam23
13322750000538256 qam24
143387500005.538256 qam26
153467500005.538256 qam27
163547500005.340256 qam28
173627500004.838256 qam29
183707500004.438256 qam30
193787500004.138256 qam31
203867500003.938256 qam32
213947500003.938256 qam34
224027500003.738256 qam35
234107500003.738256 qam36
244187500003.438256 qam37



Downstream bonded channels

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

1Locked38.9130
2Locked38.9650
3Locked38.9420
4Locked38.9260
5Locked38.9140
6Locked38.9170
7Locked38.9190
8Locked40.3160
9Locked38.970
10Locked38.6100
11Locked40.3120
12Locked38.9150
13Locked38.6110
14Locked38.9130
15Locked38.980
16Locked40.3140
17Locked38.9200
18Locked38.6240
19Locked38.9260
20Locked38.9210
21Locked38.990
22Locked38.9100
23Locked38.9180
24Locked38.9180

 

Upstream bonded channels

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

13260000038.5512064 qam5
24620000039512064 qam3
33940000038.8512064 qam4
42580000538.3512064 qam6



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
FBW
  • 6
  • 0
  • 1
Tuning in
217 Views
Message 3 of 9
Flag for a moderator

Re: Packet loss / drop outs

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt062-b.cm



Primary Downstream Service Flow

SFID783218
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID783217
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

 

Network Log

Time Priority Description

12/07/2021 10:23:4noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 05:06:55ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/07/2021 16:53:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/07/2021 05:06:54ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2021 18:36:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2021 17:06:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/06/2021 21:43:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/06/2021 13:39:25Warning!TEK Invalid - Invalid Key Sequence Number;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 22:09:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 05:06:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/06/2021 21:10:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/06/2021 17:06:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 16:55:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 05:06:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/06/2021 04:47:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 17:06:51ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 12:56:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 05:06:51ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2021 04:28:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
FBW
  • 6
  • 0
  • 1
Tuning in
213 Views
Message 4 of 9
Flag for a moderator

Re: Packet loss / drop outs

This is my BQM (Only started it a few hours ago and this one should be live)

https://www.thinkbroadband.com/broadband/monitoring/quality/share/9c7849cfabcc3762db1bc109b1362aaf49...

 

0 Kudos
Reply
sophist
  • 2.55K
  • 420
  • 683
Very Insightful Person
Very Insightful Person
160 Views
Message 5 of 9
Flag for a moderator

Re: Packet loss / drop outs

the BQM is odd. the spikes are very evenly spaced, like there's a scheduled task running every xx minutes that is maybe saturating your upload capacity (and thereby causing hte symptoms you describe..)

The power levels etc. all look fine.

i know you say you haven't added any new devices since the issue started, but is it possible that you/someone in the household has installed some new software that is uploading some data every xx minutes?

FBW
  • 6
  • 0
  • 1
Tuning in
119 Views
Message 6 of 9
Flag for a moderator

Re: Packet loss / drop outs

Interesting point.

I'm testing with only one device connected which is the PC I am messaging from. I know 100% that this PC is not always on, and is not configured with any scripts to trigger uploading of any kind.
0 Kudos
Reply
sophist
  • 2.55K
  • 420
  • 683
Very Insightful Person
Very Insightful Person
111 Views
Message 7 of 9
Flag for a moderator

Re: Packet loss / drop outs


@FBW wrote:
Interesting point.

I'm testing with only one device connected which is the PC I am messaging from. I know 100% that this PC is not always on, and is not configured with any scripts to trigger uploading of any kind.

this is a sensible way to test - if everything is OK with just the PC connected, add another device and keep adding them back until you see symptoms again… or conversely, see if you have still have the symptoms with just the PC connected, if you do - disconnect the PC and see if they persist… etc..

FBW
  • 6
  • 0
  • 1
Tuning in
100 Views
Message 8 of 9
Flag for a moderator

Re: Packet loss / drop outs

My problem might have been fixed based on the testing method suggested. Will keep monitoring and updating. I found no issues in router mode aside from the lack of speed 😞 (Reason I went in modem mode in the first place)

I've switched back and it seems like it's all okay for now...

sophist
  • 2.55K
  • 420
  • 683
Very Insightful Person
Very Insightful Person
96 Views
Message 9 of 9
Flag for a moderator

Re: Packet loss / drop outs


@FBW wrote:

My problem might have been fixed based on the testing method suggested. Will keep monitoring and updating. I found no issues in router mode aside from the lack of speed 😞 (Reason I went in modem mode in the first place)

I've switched back and it seems like it's all okay for now...


do come back and let us know what it was if everything remains stable (helps when others are experiencing similar issues :))

0 Kudos
Reply