Hub 3 cannot change DHCP Address to 192.168.1.0

[agile]

Trying to change the DHCP starting address on the HUB 3. IT is currently 192.168.0.10, when i set it to 192.168.1.10 it fails with "ip address is invalid" error. Changing to 192.168.2.0 works fine.

No idea what is going on, any clues?

[Client62]

I tried to use 192.168.1.10 as an easy way to migrate from PlusNet, but same as you, no dice from the Hub 3.

192.168.1.100 would be the IP of the Hub's menu in Modem mode, perhaps that range is reserved.

[agile]

Thanks. I think modem mode is 192.168.100.1 but it does seem like its reserved or something like that so its not allowed. I guess I will have to find a way around it

[jbrennand]

---

@agile wrote:

Thanks. I think modem mode is 192.168.100.

---

It is.👍

[asim18]

I believe you need to set the IP address of the router to 192.168.1.1 before trying to adjust the DHCP range to 192.168.1.10

OR

If you want to use DHCP range 192.168.1.10 with a dhcp server running on 192.168.0.1 I think you need to expand the subnet mask from 255.255.255.0 to 255.255.254.0

[Roger_Gooner]

Changing the address to 192.168.2.0 means addresses will be allocated on a different subnet. This is inadvisable and you should have a starting address from 192.168.0.2 and ending up to 192.168.0.254. The latter is too high if you wish to reserve static IP addresses as they should be outside the DHCP reservation range.

[legacy1]

Whats the big deal of wanting to change LAN gateway? VM don't care DHCP for anything will work any device that can't change its IP should it not use DHCP to another IP manually is not supported by VM and VM only care about DHCP devices.

If you really like 192.168.1.1  as a gateway look to get your own router 

[Tudor]

VM for some time have stopped users changing the LAN IP range to anything other than 192.168.0.0/24. You have to live with it, if you want any other ones you need to get your own router and run in modem mode.

[Anonymous · Accepted solution]

Except, the OP claims that changing the subnet to 192.168.2.0 (presumably /24) works OK. Which suggests that, at least on the Hub 3 it is still possible to change the LAN IP subnet.

The reason they can’t use the 192.168.1.0/24 range is because it is reserved for the guest WiFi network and this is still the case even if you aren’t using the guest WiFi. Alas there is no way round it, short of the modem mode, own router option.

[Client62]

Who or what is Anonymous this forum account appears to differ from all the rest ?