on 22-07-2021 08:55
I put my Hub 3.0 in Modem Mode, but there seems to be a conflict between the 192.168.100.1 address it uses for the admin web page access and the VPN I have to use to access work (I'm a 100% at home worker, even without the COVID thing). If I try to access 192.168.100.1 with the VPN on it times out, and if I turn the VPN on it doesn't. The company must be using 192.168.100.x on it's internal network and routing all of that traffic into the VPN. I can access other machines on my internal network that runs on 192.168.4.x just fine. Apart from begging the IT gods at the company to put the other machines on a 10.x.y.z range does anyone have any ideas?
on 22-07-2021 09:06
on 22-07-2021 09:50
I was hoping there was a workaround, but I guess it's on/off VPN in future for me then. I've been accessing the router quite a lot recently as it seems to be rebooting itself once a day around 11:00am. I did a pinhole reset yesterday at the request of support to try to solve it but I'm not holding my breath.
on 22-07-2021 11:08
on 22-07-2021 12:20
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 282750000 | Locked |
Ranged Upstream Channel (Hz) | 53700024 | Locked |
Provisioning State | Online |
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 282750000 | 7.3 | 40 | 256 qam | 19 |
2 | 138750000 | 8 | 40 | 256 qam | 1 |
3 | 146750000 | 7.8 | 40 | 256 qam | 2 |
4 | 154750000 | 8 | 40 | 256 qam | 3 |
5 | 162750000 | 8 | 40 | 256 qam | 4 |
6 | 170750000 | 8.3 | 40 | 256 qam | 5 |
7 | 178750000 | 8.3 | 40 | 256 qam | 6 |
8 | 186750000 | 8.4 | 40 | 256 qam | 7 |
9 | 194750000 | 8.3 | 40 | 256 qam | 8 |
10 | 202750000 | 8.3 | 40 | 256 qam | 9 |
11 | 210750000 | 8.1 | 40 | 256 qam | 10 |
12 | 218750000 | 8 | 40 | 256 qam | 11 |
13 | 226750000 | 8 | 40 | 256 qam | 12 |
14 | 234750000 | 7.5 | 40 | 256 qam | 13 |
15 | 242750000 | 7.5 | 40 | 256 qam | 14 |
16 | 250750000 | 7.4 | 40 | 256 qam | 15 |
17 | 258750000 | 7.5 | 40 | 256 qam | 16 |
18 | 266750000 | 7.4 | 40 | 256 qam | 17 |
19 | 274750000 | 7.4 | 40 | 256 qam | 18 |
20 | 290750000 | 7.1 | 40 | 256 qam | 20 |
21 | 298750000 | 7 | 40 | 256 qam | 21 |
22 | 306750000 | 6.8 | 40 | 256 qam | 22 |
23 | 314750000 | 6.5 | 40 | 256 qam | 23 |
24 | 322750000 | 6.5 | 40 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 5 | 0 |
2 | Locked | 40.3 | 5 | 0 |
3 | Locked | 40.9 | 5 | 0 |
4 | Locked | 40.3 | 5 | 0 |
5 | Locked | 40.9 | 0 | 0 |
6 | Locked | 40.3 | 17 | 0 |
7 | Locked | 40.9 | 19 | 0 |
8 | Locked | 40.3 | 5 | 0 |
9 | Locked | 40.9 | 4 | 0 |
10 | Locked | 40.3 | 19 | 0 |
11 | Locked | 40.9 | 5 | 0 |
12 | Locked | 40.9 | 6 | 0 |
13 | Locked | 40.3 | 4 | 0 |
14 | Locked | 40.3 | 6 | 0 |
15 | Locked | 40.3 | 4 | 0 |
16 | Locked | 40.9 | 0 | 0 |
17 | Locked | 40.9 | 4 | 0 |
18 | Locked | 40.3 | 6 | 0 |
19 | Locked | 40.9 | 6 | 0 |
20 | Locked | 40.9 | 6 | 0 |
21 | Locked | 40.3 | 8 | 0 |
22 | Locked | 40.9 | 4 | 0 |
23 | Locked | 40.3 | 5 | 0 |
24 | Locked | 40.3 | 5 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700024 | 33 | 5120 | 64 qam | 13 |
2 | 25799981 | 31.5 | 5120 | 64 qam | 12 |
3 | 32600007 | 31.5 | 5120 | 64 qam | 11 |
4 | 39399996 | 31.5 | 5120 | 64 qam | 10 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
General Configuration
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | Bsgvca69834ncxv9873254k;fg87d |
on 22-07-2021 12:22
Primary Downstream Service Flow
SFID | 198 |
Max Traffic Rate | 230000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 197 |
Max Traffic Rate | 22000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
Network Log
Time Priority Description
21/07/2021 12:03:1 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 12:02:51 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 11:20:59 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 02:08:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 12:35:43 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 11:17:52 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 11:44:2 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 11:28:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 11:00:38 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 06:47:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 10:38:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 18:32:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 09:18:38 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 05:06:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/07/2021 18:30:40 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/07/2021 18:30:40 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/07/2021 23:13:21 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/07/2021 13:35:1 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/07/2021 01:20:22 | 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; |
09/07/2021 01:19:35 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Monitor:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/e12f5f37593e4f86bd5184f07c2a266ce1c1c095
on 22-07-2021 12:25
And it did reboot again today, I was out. This is the uptime at 12:25pm on July 22:
Hub 3.0 device information
The information below shows current status of this Hub 3.0.
Standard specification compliant | : DOCSIS 3.0 |
Hardware version | : 10 |
Software version | : 9.1.1912.304 |
Cable MAC address | : **:**:**:**:**:** |
Cable modem serial number | : AAAP83563498 |
System up time | : 0 days 1h:57m:31s |
Network access | : Allowed |
22-07-2021 12:39 - edited 22-07-2021 12:41
Your upstream power is too low! - VM will need to book a tech visit to rectify!
Hang tight and forum staff should pick this up presently!
Basically, what's happening is: Because of the low power, your hub cannot hold a good connection to the cabinet and so tries to renegotiate with it to get a better signal - this looks like a hub reboot and takes about 5 minutes - If the renegotiated power is still too low - it tries it all again. Leading to a very unstable connection.
on 22-07-2021 12:55
Interesting, thanks. We had a tech visit a couple of weeks ago for this same problem, and he redid the cable connection at the house due to a misalignment (at least that's what I think he said) and even went to the cabinet on the street and checked and changed stuff there. It was OK for a day or two (I think) but since then it's been 10am to 11am pretty much every day that it disconnects, all the lights go out and it starts flashing, then it comes back up 5 minutes later with zero uptime in the status screen.
on 22-07-2021 12:56