Hub 4 - Modem mode stopped working at midnight, and now it won't reconnect

[phillirm]

Hi,

I've had my hub 4 in modem mode for the last few months, and it's been mostly fine. 

Last night at midnight, according to BBQM, I lost connectivity.

This morning, I've restarted everything; hub 4 lan disconnected, hub 4 powered off, hub 4 powered on, left to settle for 5 mins, router connected to port 1.

I can see the dhcp client on the router get a 192.168.100.155 address, which it renews 2 or 3 times,  but it never gets a WAN ip address assigned (the rebind fails) 

As a test: I've reset the home hub to factory settings, set it back up in router mode, and everything has worked.

I've reset the hub back to factory settings, and set it back up from scratch as a modem, just like I did first time, but it's not worked. 

Does anyone have any ideas please?  

[Tudor]

Looks like you WAN IP address has changed when in modem mode. Go through the set up again:

How to put a VM hub into modem mode:

1) Access your hub on 192.168.0.1, sign on and put it into modem mode. On the Hub3 the bottom LED will change to magenta, on a Hub4 the LED band will be green. Best done from a wired connection.

2) Turn off the hub and disconnect any Ethernet cables

3) Fully initialise your own router or mesh master unit and make sure the WAN port is set to DHCP

4) Connect your router or mesh master unit to the VM hub with an Ethernet cable, Cat5e or Cat6, any higher specification is a waste of money

5) Turn on the VM hub.

6) You should now be able to access the internet and the hub will now be on 192.168.100.1

Note1: this only needs doing once for each new router or VM changes your WAN IP address.

Note2: If you have a Hub4 and your own router is NOT 192.168.0.1 then it’s possible that you can still access the VM hub on 192.168.0.1