Forum Discussion

cookd53's avatar
cookd53
On our wavelength
2 years ago

Latency Spikes

Ever since I renewed my contract and went from a Superhub 3 to Superhub 4, I have been getting latency spikes.  I have been monitoring this since 9th December and it happens every day.  If I am on a conference call or I'm streaming video, it causes the connection to stutter, sometimes streaming has to be restarted.  Do you know what could be causing this?

 

 

  • cookd53's avatar
    cookd53
    12 months ago

    After playing around, I have identified the problem. I think the Deco S7 main box was causing the issue.  I did a  factory reset of the VM box and kept it in router mode. I then swapped the cables so that the main deco box was not between the switch and VM box and set it to Access Point mode. It's been over a week now and there have been no noticeable dropouts.

    Before:

    Deco satellites -> switch -> Deco main (Router Mode) -> VM Router (Modem Mode)

    Now:

    Deco Satellites + Deco Main (AP Mode) -> Switch -> VM box (Router Mode)

    Hopefully this will help others experiencing the same problem.

     

  • jbrennand's avatar
    jbrennand
    Very Insightful Person
    2 years ago

    What devices have you got connected to the Hub on ethernet cables?

    Lets see the connection data - can you do this...

    In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle of the Login page.
    Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts

  • cookd53's avatar
    cookd53
    On our wavelength
    2 years ago

    The VM router is connected to a deco mesh hub.  This is connected to a switch and there are various devices connected to the switch including; sky boxes, laptops, TV's, consoles.

  • cookd53's avatar
    cookd53
    On our wavelength
    2 years ago

    3.0 Downstream channels

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

    253310000003.29999940.366287QAM25625
    11390000005.59999840.366287QAM2561
    21470000005.09999840.946209QAM2562
    31550000005.00000040.946209QAM2563
    41630000004.80000340.946209QAM2564
    51710000004.59999840.946209QAM2565
    61790000004.59999840.946209QAM2566
    71870000004.69999740.946209QAM2567
    81950000004.59999840.946209QAM2568
    92030000004.40000240.366287QAM2569
    102110000004.69999740.366287QAM25610
    112190000004.69999740.946209QAM25611
    122270000004.50000040.946209QAM25612
    132350000004.40000240.946209QAM25613
    142430000004.40000240.946209QAM25614
    152510000004.19999740.366287QAM25615
    162590000004.19999740.946209QAM25616
    172670000003.90000240.946209QAM25617
    182750000003.59999840.366287QAM25618
    192830000004.09999840.946209QAM25619
    202910000004.59999840.946209QAM25620
    212990000004.80000340.946209QAM25621
    223070000004.50000040.946209QAM25622
    233150000003.90000240.946209QAM25623
    243230000003.40000240.946209QAM25624
    263390000003.59999840.946209QAM25626
    273470000003.70000140.946209QAM25627
    283550000003.50000040.946209QAM25628
    293630000003.59999840.366287QAM25629
    303710000003.79999940.366287QAM25630
    313790000003.70000140.946209QAM25631



    3.0 Downstream channels

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

    25Locked40.36628700
    1Locked40.36628700
    2Locked40.94620900
    3Locked40.94620900
    4Locked40.94620900
    5Locked40.94620900
    6Locked40.94620900
    7Locked40.94620900
    8Locked40.94620900
    9Locked40.36628700
    10Locked40.36628700
    11Locked40.94620900
    12Locked40.94620900
    13Locked40.94620900
    14Locked40.94620900
    15Locked40.36628700
    16Locked40.94620900
    17Locked40.94620900
    18Locked40.36628700
    19Locked40.94620900
    20Locked40.94620900
    21Locked40.94620900
    22Locked40.94620900
    23Locked40.94620900
    24Locked40.94620900
    26Locked40.94620900
    27Locked40.94620900
    28Locked40.94620900
    29Locked40.36628700
    30Locked40.36628700
    31Locked40.94620900
  • cookd53's avatar
    cookd53
    On our wavelength
    2 years ago

    3.0 Upstream channels

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

    14960000044.5205995120 KSym/sec64QAM9
    22360000048.0205995120 KSym/sec64QAM13
    33010000046.5205995120 KSym/sec64QAM12
    43660000045.5205995120 KSym/sec64QAM11
    54310000045.0205995120 KSym/sec64QAM10



    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1US_TYPE_ATDMA0000
    2US_TYPE_ATDMA0000
    3US_TYPE_ATDMA0000
    4US_TYPE_ATDMA0000
    5US_TYPE_ATDMA0000
  • cookd53's avatar
    cookd53
    On our wavelength
    2 years ago

    Network Log

    Time

    Priority

    Description

    Fri Jan
    19

    6

    CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan
    19

    5

    Lost MDD Timeout;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan
    19

    6

    CM-STATUS message sent. Event Type Code: 21; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan
    19

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan
    19

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan
    19

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Jan
    17

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Jan
    17

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan
    16

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan
    16

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan
    16

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan
    16

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan
    16

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Mon Jan
    15

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Mon Jan
    15

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Mon Jan
    15

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sun Jan
    14

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan
    13

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan
    13

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan
    13

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Thu Jan
    11

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Thu Jan
    11

    6

    CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Thu Jan
    11

    3

    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Thu Jan
    11

    6

    CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Jan
    10

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Jan
    10

    6

    CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Jan

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Fri Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Thu Jan

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Jan

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Mon Jan

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Dec
    30

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Dec
    30

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sat Dec
    30

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Dec
    27

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Wed Dec
    27

    6

    US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Dec
    26

    6

    DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Tue Dec
    26

    4

    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sun Dec
    24

    3

    No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    Sun Dec
    24

    6

    CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

     

  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 years ago

    run a long ping test in cmd by wire

    ping -n 500 194.168.4.100

    • cookd53's avatar
      cookd53
      On our wavelength
      2 years ago

      I ran this for a couple of minutes and towards the end there is a timeout.  I have run this on a laptop connected directly to the back of the VM router.

      Pinging 194.168.4.100 with 32 bytes of data:
      Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=14ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=6ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=6ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=6ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=12ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=12ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=14ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Request timed out.
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
      Reply from 194.168.4.100: bytes=32 time=10ms TTL=61

  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 years ago

    I would think you would see more timeouts going by your BQM unless its really low packet loss

    odd that your TTL is 61 and not 62 if you really did go to hub in modem mode

    • cookd53's avatar
      cookd53
      On our wavelength
      2 years ago

      The VM router is in router mode, not modem mode.

      • Beth_G's avatar
        Beth_G
        Forum Team
        2 years ago

        Hi cookd53

        Thank you for your post, welcome to the Community Forums.

        I'm sorry to hear you've been experiencing some issues with your connection.

        I've looked into this for you on our end and can see that there is currently an active SNR (service to noise ratio) in your area. This will be causing you slow speeds and an intermittent connection. The good news is that this issue is estimated to be fixed later this evening, so please do let us know how things are a bit later/tomorrow and we can go from there.

        Sorry again for the inconvenience this will have caused over the weekend

  • cookd53's avatar
    cookd53
    On our wavelength
    12 months ago

    After playing around, I have identified the problem. I think the Deco S7 main box was causing the issue.  I did a  factory reset of the VM box and kept it in router mode. I then swapped the cables so that the main deco box was not between the switch and VM box and set it to Access Point mode. It's been over a week now and there have been no noticeable dropouts.

    Before:

    Deco satellites -> switch -> Deco main (Router Mode) -> VM Router (Modem Mode)

    Now:

    Deco Satellites + Deco Main (AP Mode) -> Switch -> VM box (Router Mode)

    Hopefully this will help others experiencing the same problem.

     

  • jpeg1's avatar
    jpeg1
    Alessandro Volta
    12 months ago

    Is the Deco acting as a router? If so the VM Hub should be in modem mode. Feeding one router with another can cause problems.

    Edit. Just read your post again. Ignore!