I've recently implemented the sophos UTM firewall running as a VM under esxi on a minipc in place of a standalone router/ap.
The obi's are defined in the UTM's DHCP server with specific IP's under static assignments.
During testing, I changed the assigned ip's in UTM then rebooted the OBI's. The expected behavior was to receive the new ip address. Instead, both devices retained the previous IP's. I tested the same with a PC. Each time the PC received the new IP address correctly.
After much hair pulling I found an option in settings, System Management > WAN settings, Addressing type. The options are dhcp, static and pppoe. I didn't have to change anything here, but toggling the default check box then rebooting allowed the obi to pull the new ip.
This didn't make much sense. Especially the retaining of the previous ip assignment. I suppose it's a failsafe in case the obi can't get a new ip, it falls back to the last previous assignment.
I've yet to see how this works on my old router (netgear R7000). It was set up similarly. I try to keep away from static assignments on the clients themselves because it makes management that much more difficult. Keeping all the [static] assignments in one place on the dhcp server makes the most sense.
Any thoughts on the above issue?
------------
Small update. Performed the same test with my old router (netgear r7000), exact same results. In fact, it seems the only way to get it to accept the new dhcp assignment without messing with settings is to power cycle the obi's.
This thread was automatically locked due to age.
