on 14-03-2022 22:16
Hi all,
I’ve got a Hub 4 that is in modem mode connected to a TPlink Archer AX50 router. All is good speed wise and wi-fi coverage but I have one issue. The hub 4 is still on 192.168.0.1 and also on 192.168.100.1. Has anyone else had this happen to them? How do I change it?
Thanks
Answered! Go to Answer
on 19-03-2022 05:54
on 14-03-2022 22:26
on 14-03-2022 22:39
Only issue so far is the inability to login to my TPlink router over WiFi . I assumed the router would be on 192.168.0.1 and the hub 4 would be on the .100.1. ?
14-03-2022 23:18 - edited 14-03-2022 23:23
Are you sure your router is not 192.168.1.1?
Even with your router LAN at 192.168.0.1 you would get to your router not the hub as the router has no reason to send out the WAN
on 15-03-2022 16:24
Turns out is is but unfortunately I get this message now..
Local Management via HTTPS is disabled. Please access the device via HTTP
So not sure how to fix this now..
on 17-03-2022 17:50
Hi @Bigbadlee01
Thanks for posting on our community forum!
Are you still experiencing this issue now, how are you getting on after your last reply?
Regards
on 18-03-2022 19:06
Hi Travis_M
I still have the Hub 4 on 0.1 and 100.1 so yeah.
It’s not causing any real issues but does it mean that the DCHP server is active on the Hub 4?
on 19-03-2022 05:54
on 15-06-2022 18:27
That's a "workaround".
I came here as I've just had the exact same problem after upgrading from a Hub 3 to a Hub 4.
Hub 3 when you put it in modem mode, switches to 192.168.100.1 and releases 192.168.0.1
Hub 4 doesn't release the original router admin address - Despite the UI telling you to connect to 192.168.100.1 when it reboots into modem mode, it's still happily using 192.168.0.1 as well.
Which then clashed with the gateway address of my real router I had plugged into it. Orbi Router (Netgear) did at least sensibly switch to 192.168.1.1 - but it stuffed up all the stuff I had in the house configured with static IPs (or anything that references them - browser bookmarks, saved passwords, docker config etc).
Either a screw up with the hub4 firmware, or saves tech support from having to guess what IP the modem can be connected to on.
on 15-06-2022 20:26
You can certainly have your own router on 192.168.0.1 when the VM Hub4 is in modem mode, mine is, and it works.
1) When your router is in 192.168.0.1 and a station goes to this address the router handles the request and replies to the station.
2) When you router is on any subnet other than 192.168.0.1 and a stations goes to this address the router does its routing correctly and sends it out on its WAN address and it gets handled by the hub4 and it handles it and sends the response back to your router that in turn sends it to the station.
When 2) above happens on a Hub3 the hub just ignores the request.
Neither is an error, it’s just that the VM documentation is incorrect.