Hub 2 - Change LAN IP address of Router

[#1]

Under Advanced settings>My Network> IPv4 configuration

I change IP Address to: 192.168.100.1
DHCP server Enabled: No
I Click 'Save'

The address reverts back to 192.168.1.254

Even after restarting router.

What am I doing wrong?

[#2 · Accepted solution]

I know it shouldnt be necessary, since you're disabling DHCP , but have you tried setting the DHCP server address range to match the 192.168.100.x subnet ?

I've certainly changed the LAN IP of my Hub 2 but I would have changed the DHCP range as well.

I havent got mine connected at the moment but if the above suggestion doesnt work , I'll connect it and check it out.

[#3]

Many, many thanks MisterW !

That did the trick!

Not too intuitive how to get into custom mode. Nothing appears to happen when you click the custom button, that's because all the action is behind the popup menu 😋

Indeed, setting the DHCP range at same time and then disabling afterwards is the answer.

[#4]

Sounds like a bug that needs squashing. I'll look to replicate and get it raised.

[#5]

---

@Rocky-Dragon wrote:

Under Advanced settings>My Network> IPv4 configuration

I change IP Address to: 192.168.100.1
DHCP server Enabled: No
I Click 'Save'

The address reverts back to 192.168.1.254

Even after restarting router.

---

In way of an update, I am unable to replicate this problem using the latest v.08 firmware. I have followed these exact steps and the changes were saved successfully without error. I was then able to access the router GUI via its new IP address (after explicitly configuring the network card as DHCP had been disabled).

I'll therefore not be passing this one through for a 'fix' as I'm unable to reproduce the problem.

[#6]

I have firmware v0.06.00.12134-PN
So an update of my router is in order.

[#7]

@Rocky-Dragon - can you confirm the last three digits of your hub serial number please? Are they '243'?

Also, be mindful that the hub will need to be the device that is responsible for the PPP/Internet connection, else it will not communicate with the management platform that is responsible for firmware updates.