on 24-01-2024 12:56
Hello
I'm already tired of that issue. Through 2 years everything was good. Last year before xmas period the pings, latency was high and unstable but still without any disconnections of the internet. After 2024 arrived the ping and latency became stable again but router starts restarting every or every second night at similar time 02:12-02:22 There is no difference if it's used at WiFi or modem mode.
I never had that kind of issue before. Please do not say about sending updates or those kinds of things because it's not really true.
I tried to do everything changing ethernet cable, restarting router, restarting by the pin at back cover, uploading previous settings, changing devices. Cables and splitters seems fine, there was even technician to change end part of the cable in the wall socket outside of the house.
The only thing which I didn't had chance to do is change the hub for the new one. Is there any chance the hub is faulty or the hub firmware?
on 24-01-2024 14:40
Lets see the data and set up a BQM - 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 (Hub3/4/5) or top/right (SH’s) - 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
Also, If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality
on 24-01-2024 22:56
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 723000000 | 6.4 | 40 | 256 qam | 40 |
2 | 539000000 | 6.4 | 40 | 256 qam | 17 |
3 | 547000000 | 6.1 | 40 | 256 qam | 18 |
4 | 555000000 | 6.1 | 40 | 256 qam | 19 |
5 | 563000000 | 6.1 | 40 | 256 qam | 20 |
6 | 571000000 | 5.6 | 40 | 256 qam | 21 |
7 | 579000000 | 5.6 | 40 | 256 qam | 22 |
8 | 587000000 | 5.5 | 40 | 256 qam | 23 |
9 | 595000000 | 5.1 | 40 | 256 qam | 24 |
10 | 603000000 | 5.6 | 40 | 256 qam | 25 |
11 | 611000000 | 5.5 | 40 | 256 qam | 26 |
12 | 619000000 | 5.5 | 40 | 256 qam | 27 |
13 | 627000000 | 5.5 | 40 | 256 qam | 28 |
14 | 635000000 | 5.1 | 40 | 256 qam | 29 |
15 | 643000000 | 5.9 | 40 | 256 qam | 30 |
16 | 651000000 | 5.5 | 40 | 256 qam | 31 |
17 | 659000000 | 5.6 | 40 | 256 qam | 32 |
18 | 667000000 | 6.1 | 40 | 256 qam | 33 |
19 | 675000000 | 6 | 40 | 256 qam | 34 |
20 | 683000000 | 6 | 40 | 256 qam | 35 |
21 | 691000000 | 6.3 | 40 | 256 qam | 36 |
22 | 699000000 | 6 | 40 | 256 qam | 37 |
23 | 707000000 | 6 | 40 | 256 qam | 38 |
24 | 715000000 | 5.9 | 40 | 256 qam | 39 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 9 | 0 |
2 | Locked | 40.9 | 13 | 0 |
3 | Locked | 40.3 | 19 | 0 |
4 | Locked | 40.3 | 13 | 0 |
5 | Locked | 40.3 | 7 | 0 |
6 | Locked | 40.3 | 10 | 0 |
7 | Locked | 40.9 | 8 | 0 |
8 | Locked | 40.3 | 6 | 0 |
9 | Locked | 40.3 | 8 | 0 |
10 | Locked | 40.9 | 6 | 0 |
11 | Locked | 40.9 | 14 | 0 |
12 | Locked | 40.3 | 12 | 0 |
13 | Locked | 40.9 | 20 | 0 |
14 | Locked | 40.3 | 9 | 0 |
15 | Locked | 40.9 | 8 | 0 |
16 | Locked | 40.3 | 8 | 0 |
17 | Locked | 40.3 | 11 | 0 |
18 | Locked | 40.9 | 9 | 0 |
19 | Locked | 40.3 | 13 | 0 |
20 | Locked | 40.3 | 20 | 0 |
21 | Locked | 40.3 | 8 | 0 |
22 | Locked | 40.3 | 7 | 0 |
23 | Locked | 40.3 | 18 | 0 |
24 | Locked | 40.3 | 26 | 0 |
on 24-01-2024 22:56
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 46.3 | 5120 | 64 qam | 11 |
2 | 23600000 | 41.3 | 5120 | 64 qam | 13 |
3 | 30100000 | 42.3 | 5120 | 64 qam | 12 |
4 | 43099957 | 43.3 | 5120 | 64 qam | 10 |
5 | 49599998 | 44.8 | 5120 | 64 qam | 9 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
on 24-01-2024 22:57
Time Priority Description
24/01/2024 02:21:54 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/01/2024 17:10:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/01/2024 15:59:26 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/01/2024 15:59:26 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 19:49:9 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 10:00:4 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 09:55:4 | 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; |
20/01/2024 09:54:18 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 09:54:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 09:54:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 09:54:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2024 09:53:5 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/01/2024 18:23:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/01/2024 09:38:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/01/2024 07:38:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/01/2024 02:22:51 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/01/2024 20:44:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/01/2024 00:33:54 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/01/2024 00:33:54 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/01/2024 19:13:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 25-01-2024 20:11
Here is first night without disconnecting.
on 27-01-2024 01:53
26/1/23
again without disconnecting which is weird is it because i swap from modem mode to wifi on ethernet cable? Otherwise i wouldn't be able to provide those network monitoring at modem mode.
on 28-01-2024 01:55
27/1/23
Still without disconnecting which is weird situation. Full month with problems and just suddenly it's stopped for now.
on 30-01-2024 02:53
Is there any chance the issue only happens during modem mode? Or modem was blocking some updates? I've been always fan of modem connections because of the better connection and pings stability.
28/1/24
29/1/24
on 30-01-2024 08:03
The current Hub 3 software is : 9.1.2208.100 ( see in Hub 3 menu at: Admin >> Info ) if your Hub 3 has this version, software updates can be ruled out.