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 14:02
on 22-07-2021 14:07
on 24-07-2021 14:37
OK, I called in after setting it back to router mode, and the person I spoke to "enabled the other bands" on the cable connection. Here's the status now:
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 170750000 | Locked |
Ranged Upstream Channel (Hz) | 53700026 | Locked |
Provisioning State | Online |
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 170750000 | 8.4 | 40 | 256 qam | 5 |
2 | 138750000 | 8 | 40 | 256 qam | 1 |
3 | 146750000 | 7.9 | 40 | 256 qam | 2 |
4 | 154750000 | 8 | 40 | 256 qam | 3 |
5 | 162750000 | 8 | 40 | 256 qam | 4 |
6 | 178750000 | 8.4 | 40 | 256 qam | 6 |
7 | 186750000 | 8.5 | 40 | 256 qam | 7 |
8 | 194750000 | 8.4 | 40 | 256 qam | 8 |
9 | 202750000 | 8.4 | 40 | 256 qam | 9 |
10 | 210750000 | 8.3 | 40 | 256 qam | 10 |
11 | 218750000 | 8 | 40 | 256 qam | 11 |
12 | 226750000 | 8 | 40 | 256 qam | 12 |
13 | 234750000 | 7.6 | 40 | 256 qam | 13 |
14 | 242750000 | 7.5 | 40 | 256 qam | 14 |
15 | 250750000 | 7.5 | 40 | 256 qam | 15 |
16 | 258750000 | 7.5 | 40 | 256 qam | 16 |
17 | 266750000 | 7.5 | 40 | 256 qam | 17 |
18 | 274750000 | 7.4 | 40 | 256 qam | 18 |
19 | 282750000 | 7.3 | 40 | 256 qam | 19 |
20 | 290750000 | 7.3 | 40 | 256 qam | 20 |
21 | 298750000 | 7 | 40 | 256 qam | 21 |
22 | 306750000 | 6.9 | 40 | 256 qam | 22 |
23 | 314750000 | 6.6 | 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 | 6 | 0 |
3 | Locked | 40.9 | 4 | 0 |
4 | Locked | 40.3 | 6 | 0 |
5 | Locked | 40.9 | 0 | 0 |
6 | Locked | 40.9 | 0 | 0 |
7 | Locked | 40.3 | 20 | 0 |
8 | Locked | 40.3 | 17 | 0 |
9 | Locked | 40.9 | 5 | 0 |
10 | Locked | 40.3 | 6 | 0 |
11 | Locked | 40.9 | 6 | 0 |
12 | Locked | 40.9 | 5 | 0 |
13 | Locked | 40.3 | 5 | 0 |
14 | Locked | 40.3 | 5 | 0 |
15 | Locked | 40.9 | 1 | 0 |
16 | Locked | 40.9 | 5 | 0 |
17 | Locked | 40.9 | 4 | 0 |
18 | Locked | 40.3 | 5 | 0 |
19 | Locked | 40.3 | 5 | 0 |
20 | Locked | 40.3 | 5 | 0 |
21 | Locked | 40.3 | 5 | 0 |
22 | Locked | 40.9 | 5 | 0 |
23 | Locked | 40.3 | 6 | 0 |
24 | Locked | 40.3 | 0 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700026 | 31.5 | 5120 | 64 qam | 13 |
2 | 25799981 | 31.5 | 5120 | 64 qam | 12 |
3 | 32600002 | 31.5 | 5120 | 64 qam | 11 |
4 | 39400012 | 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 |
on 24-07-2021 14:38
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | ewrkldJKDHSUBsgvca69834ncxv98 |
SFID | 198 |
Max Traffic Rate | 230000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 197 |
Max Traffic Rate | 22000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
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; |
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; |
on 24-07-2021 15:12
on 24-07-2021 15:19
on 24-07-2021 15:24
I'm using Modem mode usually, I just put it in Router mode temporarily based on advice earlier to put it in Router mode to let them look at it better. I have it in Modem mode with a 1m Ethernet connection to an Eero mesh system with three stations, one at the router at the front of the house, one in my boxroom/home office in the room above the router, and one in the kitchen/dining at the back of the house. I just got bumped up to 200/20 and it tests at that on Speedtest.net even on my iPhone 11 basically anywhere in the house now.
on 24-07-2021 15:54
Hi @minispiney,
Welcome to our Community Forums and thanks for posting.
I have taken a look at your account and can see your upstream signal levels are out of specification. We would need to send a technician out to get this corrected.
Will pop you a PM now so we can confirm your address and take things from there 🙂
on 24-07-2021 16:03
@minispiney wrote:I have it in Modem mode with a 1m Ethernet connection to an Eero mesh system
OK - I dont know much about the Eero's routing capabilities for maintaining a VPN connection - someone else needs to comment on that.
You are getting a Tech visit now though to sort the Up power levels - that should sort any network disconnection issues - lets see if it sorts the VPN connectivity too.
24-07-2021 16:24 - edited 24-07-2021 16:28
@minispiney wrote:I put my Hub 3.0 in Modem Mode, but there seems to be a conflict between the 192.168.100.1....
Ok for there to be a conflict your router LAN would have to be setup for 192.168.0.0/24 or 192.168.100.0/24 if your works VPN subnet is 192.168.100.0/24 that is not a problem you connect to the VPN and you PC will route 192.168.100.0/24 down the VPN with no conflict to the hub at 192.168.100.1 so you can't access the hub when VPN is on.
If your subnet router LAN is 255.255.0.0 that a problem so is if the VPN subnet is bigger then 255.255.255.0 as that may over lap with your LAN IP/subnet.