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?
So the tech came out just now, and ended up changing the "transition link" (I think that's what he called it, it's a 15cm or so optical cable from the end of the fibre reel in the back of the brown box to the ONT). As he was opening it up to check he noticed that when he was moving the ONT around the light on it was going off and on. He changed that little link cable, and did a test of the connection. Apparently the ONT was changed by the previous tech. According to him the power levels are right, as we're on a fibre connection right to the house. He will ring me tomorrow to check that it's holding up.
Hi @minispiney,
Thank you for the update. I'm glad to hear that this is being looked into and addressed.
Please do let us know how things progress and how tomorrow's call goes for you.
Thanks,
Zach - Forum Team
New around here? To find out more about the Community Forums, take a look at our FAQs!
It's still doing it. It went offline/rebooted at around 2am today (now 18:00).
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 16h:13m:8s |
| Network access | : Allowed |
There's a suspicious entry in the log at about that time:
Network Log
Time Priority Description
| 30/07/2021 08:19:20 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 30/07/2021 01:44:13 | Error | Service Add Response rejected - Invalid transaction ID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 29/07/2021 12:21:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 29/07/2021 10:10:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 15:00:31 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 15:00:27 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 15:00:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 15:00:27 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 15:00:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 28/07/2021 12:54:36 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/07/2021 20:12:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 26/07/2021 09:59:49 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 26/07/2021 07:09:52 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 26/07/2021 07:09:52 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 25/07/2021 19:02:29 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 25/07/2021 12:40:57 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 25/07/2021 05:28:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 24/07/2021 13:53:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 23/07/2021 22:33:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/07/2021 12:03:1 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
The tech said he would call again tomorrow (Monday) and check in and depending on what I have seen work out what happens next. I'll update after I talk to him. It's 9am Sunday and it has been up for 2 days and 7 hours right now. It has reset on at least two occasions since the visit though.
9:50am Monday, status says uptime 1hr 7mins, so it must have done it again while I was out at exercise class this morning.
