Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Virgin Media Community
- Broadband
- Speed
- Latency Spikes
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 15:50
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?
Answered! Go to Answer
1 ACCEPTED SOLUTION
Accepted Solutions
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
10-02-2024 10:55 - edited 10-02-2024 11:02
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.
12 REPLIES 12
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 15:55
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
--------------------
John
--------------------
I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
19-01-2024 16:16 - edited 19-01-2024 16:31
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.
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 16:17
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
| 25 | 331000000 | 3.299999 | 40.366287 | QAM256 | 25 |
| 1 | 139000000 | 5.599998 | 40.366287 | QAM256 | 1 |
| 2 | 147000000 | 5.099998 | 40.946209 | QAM256 | 2 |
| 3 | 155000000 | 5.000000 | 40.946209 | QAM256 | 3 |
| 4 | 163000000 | 4.800003 | 40.946209 | QAM256 | 4 |
| 5 | 171000000 | 4.599998 | 40.946209 | QAM256 | 5 |
| 6 | 179000000 | 4.599998 | 40.946209 | QAM256 | 6 |
| 7 | 187000000 | 4.699997 | 40.946209 | QAM256 | 7 |
| 8 | 195000000 | 4.599998 | 40.946209 | QAM256 | 8 |
| 9 | 203000000 | 4.400002 | 40.366287 | QAM256 | 9 |
| 10 | 211000000 | 4.699997 | 40.366287 | QAM256 | 10 |
| 11 | 219000000 | 4.699997 | 40.946209 | QAM256 | 11 |
| 12 | 227000000 | 4.500000 | 40.946209 | QAM256 | 12 |
| 13 | 235000000 | 4.400002 | 40.946209 | QAM256 | 13 |
| 14 | 243000000 | 4.400002 | 40.946209 | QAM256 | 14 |
| 15 | 251000000 | 4.199997 | 40.366287 | QAM256 | 15 |
| 16 | 259000000 | 4.199997 | 40.946209 | QAM256 | 16 |
| 17 | 267000000 | 3.900002 | 40.946209 | QAM256 | 17 |
| 18 | 275000000 | 3.599998 | 40.366287 | QAM256 | 18 |
| 19 | 283000000 | 4.099998 | 40.946209 | QAM256 | 19 |
| 20 | 291000000 | 4.599998 | 40.946209 | QAM256 | 20 |
| 21 | 299000000 | 4.800003 | 40.946209 | QAM256 | 21 |
| 22 | 307000000 | 4.500000 | 40.946209 | QAM256 | 22 |
| 23 | 315000000 | 3.900002 | 40.946209 | QAM256 | 23 |
| 24 | 323000000 | 3.400002 | 40.946209 | QAM256 | 24 |
| 26 | 339000000 | 3.599998 | 40.946209 | QAM256 | 26 |
| 27 | 347000000 | 3.700001 | 40.946209 | QAM256 | 27 |
| 28 | 355000000 | 3.500000 | 40.946209 | QAM256 | 28 |
| 29 | 363000000 | 3.599998 | 40.366287 | QAM256 | 29 |
| 30 | 371000000 | 3.799999 | 40.366287 | QAM256 | 30 |
| 31 | 379000000 | 3.700001 | 40.946209 | QAM256 | 31 |
3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
| 25 | Locked | 40.366287 | 0 | 0 |
| 1 | Locked | 40.366287 | 0 | 0 |
| 2 | Locked | 40.946209 | 0 | 0 |
| 3 | Locked | 40.946209 | 0 | 0 |
| 4 | Locked | 40.946209 | 0 | 0 |
| 5 | Locked | 40.946209 | 0 | 0 |
| 6 | Locked | 40.946209 | 0 | 0 |
| 7 | Locked | 40.946209 | 0 | 0 |
| 8 | Locked | 40.946209 | 0 | 0 |
| 9 | Locked | 40.366287 | 0 | 0 |
| 10 | Locked | 40.366287 | 0 | 0 |
| 11 | Locked | 40.946209 | 0 | 0 |
| 12 | Locked | 40.946209 | 0 | 0 |
| 13 | Locked | 40.946209 | 0 | 0 |
| 14 | Locked | 40.946209 | 0 | 0 |
| 15 | Locked | 40.366287 | 0 | 0 |
| 16 | Locked | 40.946209 | 0 | 0 |
| 17 | Locked | 40.946209 | 0 | 0 |
| 18 | Locked | 40.366287 | 0 | 0 |
| 19 | Locked | 40.946209 | 0 | 0 |
| 20 | Locked | 40.946209 | 0 | 0 |
| 21 | Locked | 40.946209 | 0 | 0 |
| 22 | Locked | 40.946209 | 0 | 0 |
| 23 | Locked | 40.946209 | 0 | 0 |
| 24 | Locked | 40.946209 | 0 | 0 |
| 26 | Locked | 40.946209 | 0 | 0 |
| 27 | Locked | 40.946209 | 0 | 0 |
| 28 | Locked | 40.946209 | 0 | 0 |
| 29 | Locked | 40.366287 | 0 | 0 |
| 30 | Locked | 40.366287 | 0 | 0 |
| 31 | Locked | 40.946209 | 0 | 0 |
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 16:18
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
| 1 | 49600000 | 44.520599 | 5120 KSym/sec | 64QAM | 9 |
| 2 | 23600000 | 48.020599 | 5120 KSym/sec | 64QAM | 13 |
| 3 | 30100000 | 46.520599 | 5120 KSym/sec | 64QAM | 12 |
| 4 | 36600000 | 45.520599 | 5120 KSym/sec | 64QAM | 11 |
| 5 | 43100000 | 45.020599 | 5120 KSym/sec | 64QAM | 10 |
3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
| 1 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
| 2 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
| 3 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
| 4 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
| 5 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 16:25
Network Log
Time | Priority | Description |
Fri Jan | 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 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan | 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 | 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 | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 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; |
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; |
Thu Jan | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan | 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 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan | 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 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jan | 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 | 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 | 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 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec | 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 | 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 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:*;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec | 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; |
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
19-01-2024 16:29 - edited 19-01-2024 16:30
run a long ping test in cmd by wire
ping -n 500 194.168.4.100
---------------------------------------------------------------
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 16:52
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
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
19-01-2024 17:52 - edited 19-01-2024 17:56
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
---------------------------------------------------------------
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 19-01-2024 18:38
The VM router is in router mode, not modem mode.
Related Content
