How can I change my Hub 4 internal IP address from 192.168.0.x

[ruddlesdin]

How can I change my Hub 4 internal IP address from 192.168.0.x

The option is there in the Advanced - DHCP settings but no matter what number I choose (192.168.20.x or 192.168.5.x) it laways says 'The starting IP address you have entered is used for other functions of the Hub 4. Please enter another.' after apply the new settings.

It appears I am stuck with 192.168.0.x and I don't want to be as it is causing conflict issues my VPN service

[legacy1]

No VPN service I know of uses 192.168.0.x

If you want to change this you can get your own router with1Gb ports and put hub in modem mode 

[ruddlesdin]

Is there anyone who can offer any suggestions that don't involve putting the hub in modem mode and buying a new router?

[Client62]

Your comment about a VM Hub DHCP range of 192.168.0.xxx clashing with the VPN is not going to be true.

I've spent three decades in the IT industry, and never once have I asked a person with an office laptop what is the IP range of your home internet. Why ? Because it is expected to be totally unknown and we expect our office VPNs to work perfectly with what ever folk have at home and what ever they use at a hotel or airport.

[Roger_Gooner]

You need to say what conflict issues you are having.

[marcuspd]

Well you've lived a very sheltered career then, because loads of SMALL businesses have the range in 192.168.0.x/28 . This is a stupid idea from Virgin Media and causing me tons of issues. I found this post, because they're trying to change my home address to one. 

They're useless to anyone trying to route VPN to a remote network on 192.168.0.x/28, which contrary to all the supposed "experts" on here, so exist. I have at least 6 business customers using it and almost as many using 192.168.1.x/28. 

What's the point if I end up having to use it in modem mode, so I can put a Draytek or any basic function £20 router which has more flexibility than the naff and useless Hub 4? 

[marcuspd]

Easy. VPN can only route properly if remote and local subnets are on a different range. 

If both remote and local are using 192.168.0.x/28, when the local PC wants to fins a resource (say 192.168.0.100) on the remote network, the PC and router doesn't know whether it will be on the local network, or to route it through the VPN tunnel to the remote network, as both use the same IP range. 

Older hubs let you change the local subnet to something more unique, not the same as almost every other router out of the box, uses. 

[legacy1]

---

@marcuspd wrote:

Well you've lived a very sheltered career then, because loads of SMALL businesses have the range in 192.168.0.x/28 .

---

and they also know many home routers use 192.168.0x/24

[Client62]

"lived a very sheltered career then"  ... A good job I've had my G&T that is pathetic.

[Matthew_ML]

Thank you for posing number-6. are you also having issues with this?