Forum Discussion

LS95's avatar
LS95
Tuning in
2 years ago

Wifi is terrible and constantly dropping even after boosters

CONSTANT problems with the WiFi i swear it has been throughout the entire of my contract, at first i thought it was just the 360 tv box however it is now all devices connected via WiFi, the hub has been replaced 3 times and am honestly coming to my wits end. here is the broadband monitor : 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b3034b018493904b0702b4eedb7fdae31480cedf

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13307500001.440256 qam25
22027500002.240256 qam9
32107500002.240256 qam10
42187500002.240256 qam11
5226750000240256 qam12
6234750000240256 qam13
72427500001.740256 qam14
82507500001.540256 qam15
92587500001.440256 qam16
102667500001.240256 qam17
11274750000140256 qam18
122827500000.940256 qam19
132907500000.740256 qam20
14298750000138256 qam21
15306750000140256 qam22
163147500001.240256 qam23
173227500001.240256 qam24
183387500001.740256 qam26
193467500001.540256 qam27
203547500001.540256 qam28
213627500001.740256 qam29
223707500001.740256 qam30
233787500001.940256 qam31
243867500001.740256 qam32


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.92130
2Locked40.92470
3Locked40.32180
4Locked40.32300
5Locked40.32130
6Locked40.32290
7Locked40.32040
8Locked40.32160
9Locked40.32070
10Locked40.32050
11Locked40.32120
12Locked40.32050
13Locked40.32410
14Locked38.62270
15Locked40.32160
16Locked40.32260
17Locked40.32180
18Locked40.32010
19Locked40.32220
20Locked40.32320
21Locked40.32300
22Locked40.91920
23Locked40.31840
24Locked40.31810

 

9 Replies

  • Upstream bonded channels

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

    12360000032512064 qam6
    23260000032512064 qam5
    33940000032512064 qam4
    44620000032512064 qam3



    Upstream bonded channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1ATDMA0070
    2ATDMA0030
    3ATDMA0040
    4ATDMA0010
  • Network Log

    Time Priority Description

    19/12/2023 01:37:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    17/12/2023 13:05:0noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    17/12/2023 13:05:0ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    14/12/2023 03:25:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    14/12/2023 01:05:0noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    14/12/2023 01:05:0ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 19:54:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:59:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:59:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:58:57Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:58:57criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:30criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:29Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:29criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:28Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:13Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:9criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:9Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    11/12/2023 11:57:9criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    • jbrennand's avatar
      jbrennand
      Very Insightful Person

      Your upstream power levels are on the low side - may be contributing to the T3 errors.

      A VM person needs to comment

      • legacy1's avatar
        legacy1
        Alessandro Volta

        jbrennand wrote:

        Your upstream power levels are on the low side - may be contributing to the T3 errors.


        Not really the BQM shows ok we don't know how long the hub has been on when T3 happened unlike SH1 where the counter reset every 24hr making it easy.😋

        I would suggest using the hub in modem mode and get your own better router with 1Gb ports

    • Gareth_L's avatar
      Gareth_L
      Icon for Forum Team rankForum Team

      Hello LS95

      Thank you very much for your post 
      Can I just apologise for the T3 errors
      We can run a few tests from here and check on your equipment.
      Sadly it's not showing anything wrong, So I will need to send you a private message to gain account access and run further tests.

      In the meantime can you reboot our hub as its been online for quite a while
      If you can check the logo top right of your screen that would be great. 
      Regards     
      Gareth_L
       

  • Hi Gareth just letting you know its been almost a week and so far all issues seem resolved, thanks again so much for the help

    • Beth_G's avatar
      Beth_G
      Icon for Forum Team rankForum Team

      Hi LS95

      Happy New Year!

      Thanks very much for the update - we're pleased to hear the issues seem to have cleared for you.

      Just double checked our end and all seems OK from here too.

      If you have any further trouble, just let us know  ðŸ˜Š