Yesterday I messed up my network after a stupid move from myself, now for some reason my main Hub is at an IP on the main vlan instead of being on the IoT vlan. Trying to RESET the network settings with the hidden button under the hub does not reset anything either. Not sure how long the lease is since I can't find this info anywhere on the hub (unless there's an endpoint I don't know of). So what I'd like to find is a way to force the hub to ask for a new DHCP lease so that it goes back to it's normally reserved IP.
Also I tried setting a static IP to at least get it working again at it's normal IP, but that does not seem to work at all most likely since it's on a different subnet, also tried using 255.255.0.0 as a subnet mask but that did not work either
.
@nclark Set the hub to DHCP then put a reservation into your DHCP server to a desired IP. (Note, most home routers require the reservation within the scope, not outside)
It's been like that for years and my network is a full blown Omada network, I tried rebooting and all but the hub keeps wanting to stay on the IP settings it got yesterday when it was all messed up. Had to reset the router to factory settings before adopting it back in the network, that is when the hub got an IP or something and since then it won't take the reservation set in the DHCP server.
I thought that a reboot would clear all network settings and ask for a new lease, but that does not seem to be the case, right now I shutdown the hub and keeping it off power for a few minutes just to see. All my other C5 hubs have changed their IPs pretty fast when the router was back to normal, but my main C7 seems to be a bit stubborn!
This!!! I agree that it sounds like the port the hub is plugged into is configured for the wrong VLAN.
